Shadow
It watches. You work.
Tensvia drafts replies you never have to use. You keep running your business exactly as you do today while we measure your real response time.
- Sends without you
- Nothing
Tensvia answers every inquiry across Instagram, text, WhatsApp and email — in your voice, with your prices and your hours. You approve every reply until you decide you don't need to.
No cold spam. No bans. Nothing sends without you.
Priced from your service list · availability from your calendar
Nothing leaves this screen until you tap.
One queue. Every channel your customers actually message you on.
How it works
Link the channels you actually use. About two minutes each, and nothing is read until you say go.
Your services, prices, hours and policies become the only facts Tensvia is allowed to answer from.
Every inquiry gets classified and a reply drafted. You read it, edit it, send it. Nothing moves without you.
Once you trust it, let the routine questions answer themselves — category by category, on your terms.
You stay in control
The real worry isn't whether AI can write a reply. It's whether it will say something stupid to your customer. So you decide how much rope it gets, and you can take it back at any point.
It watches. You work.
Tensvia drafts replies you never have to use. You keep running your business exactly as you do today while we measure your real response time.
It drafts. You send.
Every reply lands in a queue with the reasoning attached. One tap sends it, one tap rewrites it. This is where most owners stay for a while, and that's fine.
It handles the easy ones.
You pick which categories can answer themselves — hours, pricing, availability. Anything outside those lines still comes to you.
how long a pricing DM sat unanswered on our own account
Why this exists
Not a hypothetical. That message was a booking, and it went somewhere else. We built Tensvia for our own business first, then made it something you can buy.
You won't find invented percentages on this page. When the pilot numbers are real, they'll go here — and until then the audit is how you get a number that's actually yours.
Safeguards
Mass-DM tools get shut down because they treat consent as a setting. Here it's enforced below the application, where nothing can route around it.
Not in a prompt. An opted-out contact cannot be messaged, even if something upstream tries.
What was proposed, why, who approved it, when it sent. You can always answer 'why did it say that?'
The model drafts and classifies. It cannot send, spend, or reach another business's data. Sending is a separate, gated step.
Drop back to Shadow mode at any point. No migration, no lock-in, and your CRM stays your CRM.
A real trail from a real reply. Every message you send has one.
Pricing
If the audit says you don't have a response-time problem, we'll tell you and you can stop there. That happens, and it's a fine outcome.
We measure what a slow reply is actually costing you.
Your channels connected, your knowledge loaded, your queue live.
Monitoring, tuning, and someone who picks up the phone.
Messaging and model usage billed at cost, never marked up.
FAQ
No. Tensvia only replies to people who messaged you or opted in. Consent lives in the database, not in an instruction the model could talk its way around. Opt-outs are permanent and enforced before any send.
In Shadow and Approval mode it cannot send anything at all — you do. It also answers only from the services, prices and hours you loaded, so it has nothing to invent from. When it isn't confident, it escalates instead of guessing.
Keep them. Tensvia plugs into what you have and writes back to it. Replacing your system of record is explicitly out of scope, and we'd rather say that up front than discover it in month two.
ChatGPT can't see your Instagram DMs, doesn't know today's prices, doesn't log what it sent, and won't stop you from texting someone who opted out. Those four things are the entire job.
Automation fires a fixed sequence. Tensvia reads the message, decides what kind of message it is, and routes the ones it shouldn't touch to you — with its reasoning attached so you can check its work.
The audit is $400. Implementation runs $750–2,000 depending on how many channels you use. Ongoing is $75–250 a month. Messaging and model usage are billed at cost, not marked up.
Safeguards
Anyone can generate a reply. The work is in what stops one from going out. These are mechanisms, not badges — we hold no SOC 2 report or ISO certificate yet, and we would rather say so than imply otherwise.
Not in a prompt the model could be talked around. Consent state is a row, checked before every send, and it fails closed — a missing record is treated as no consent, never as unknown.
STOP, unsubscribe and revocation are recorded and enforced before any outbound send, on every channel. There is no campaign setting that overrides them.
Until you move a workflow to autonomy, every message is drafted and held. Approval records who approved it. Execution is a separate step after approval, not part of it.
Replies cite the records they were drawn from — your services, prices, hours, policies. Nothing ungrounded is presented as grounded, and you can open the source behind any sentence.
Provider keys are stored as vault references. They are never written to a log, never placed in model context, and never sent to the browser.
Isolation is enforced at the database with row-level security, not by application code remembering to filter. If the application logic fails, the database still refuses.
Held, skipped, opted out, retried. A feed that only shows what worked teaches you nothing about whether the guards are working.
Export on request in a machine-readable form, and deletion within 30 days of termination except where we are required to retain records.
Messaging compliance is shared: we build the enforcement, you are responsible for how contacts entered your list. Our Acceptable Use & Messaging Policy sets out where that line sits.
Two weeks of measurement, one honest number, and a straight answer about whether this is worth doing. $400, and we'll tell you if it isn't.