Put one agent behind calls, chat, messages, and email. It answers from your knowledge, uses approved tools, and brings your team in with the conversation intact.
No card required$79/mo for 10 team membersNo resolution fee
How one deployed agent works
Configure once. Deploy each channel independently.
Connects to the tools your team already uses
A receptionist is not a phone tree and it is not a recording. It answers the routine calls so nobody on staff gets interrupted, and hands over the moment the request is not routine. What it is allowed to do on its own is something you write down first, in plain language, before the number is ever forwarded.
How the setup worksHi, I need to move my cleaning appointment to Thursday afternoon.
I can help with that. I have your deep clean booked for the 6th. Would you like me to request Thursday afternoon instead?
Yes, and can you add the inside of the oven this time?
I've added the oven clean to your request. I'll check Thursday availability and send a confirmation once your booking is updated.
Request captured · confirmation pending
Perfect, thank you.
Opening hours, services, prices, preparation, what to bring. Grounded in the same articles your website serves, so it cannot contradict you.
Look up an order in Shopify, a contact in HubSpot, a ticket in Zendesk, or your own booking system over an API. You decide which actions it may take alone and which need a person to approve.
Matches the number to your customer record before it answers, so repeat callers are not made to repeat themselves.
When it is out of its depth, or the caller asks for a person, the human gets the transcript, the account, and what was already said.
Most companies stitch a phone system, a chatbot, and a help desk onto each other, and the customer falls through the seams. Here it is one agent with one set of instructions, so it cannot give your customer two different answers.
Give it a number or let people talk through the browser. It answers from your documents, takes messages when you are closed, and hands a human the whole transcript when the question is not a repeat one.
Give it a number or let people talk through the browser. It answers from your documents, takes messages when you are closed, and hands a human the whole transcript when the question is not a repeat one.
No engineering ticket, no data migration, no change to the way your team works. Here is the whole setup, in the order it actually happens.
Paste your website address and it reads the pages. Upload the PDFs and Word files you already send customers. Connect the Notion page your team keeps answers in.
There is nothing to rewrite or migrate. If you can email someone a document, you already have everything it needs.
Tell it who it is, when it should hand off, what it must never promise, and what to do when it is not sure. You are writing instructions, not code.
You choose how much it may do on its own: answer only, look up an order, open a ticket, or ask a person before a sensitive action.
Forward a phone number to it, drop one script tag on your site, or connect the mailbox. Each one is switched on independently, so you can start with the phone and add the rest later.
Nothing goes live that you have not switched on yourself. Pause a channel and it stops answering, instantly.
Every conversation is recorded with the exact articles it used and the tools it called. Find the question it got wrong, edit that one article, and the phone, the widget and the inbox drafts are all corrected at the same time.
This is the step that decides whether you keep it. It is also the one that costs you the least time, because the fix is an edit to a document you already own.
This is the product, in the order you would use it. Every line is live today — you can try any of it before you pay.
The full feature list, with screenshots and the limits of each plan, is on the features pages. If something you need is missing, you will find out in the trial rather than after the contract.
Most small teams end up paying for a phone AI, a chatbot, a help desk, and a docs site from four vendors, none of which share a knowledge base. SupportSiteFlow runs all four from one plan with 10 seats included and no per-resolution charge.
By this point you have read what it does. These are the four things that usually stop a team switching, and none of them require you to take our word for it.
Professional is $79 a month with 10 team members included. It is not priced per conversation or resolved ticket, and Enterprise removes the seat limit.
See the plansPhone, chat, email and the drafts in your inbox are all reading the same knowledge base. Your customer cannot get two different prices, or two different policies, depending on how they asked.
How the knowledge base worksPoint it at your website and it reads the pages. Upload the PDFs and documents you already send customers, or connect the Notion page your team keeps answers in. There is nothing to rewrite and nothing to migrate.
See the setupIt reads Zendesk, HubSpot, Shopify and Notion directly, and anything else goes through webhooks and the REST API. Start with one channel, then turn off an old subscription when you trust the answers.
See the integrationsStarter includes 3 team members. Professional includes 10. Enterprise is unlimited. Nothing here charges per conversation, resolved ticket, or call answered, and you can cancel from the dashboard without asking anyone.
One person getting a first channel live.
$29/month
$290/year, or $29 monthly
Add more people or channels whenever you need them.
Start freeThe whole platform for a team, on one flat price.
$79/month
$790/year, or $79 monthly
No charge per conversation, resolution or call answered.
Start freeBigger teams, white labelling, and a direct line.
$199/month
$1990/year, or $199 monthly
Talk to us about a dedicated migration from your current tool.
Talk to usNot sure which one you need?
Turn on one channel and use it free. Most teams know within a week, and every included seat is visible before you choose a plan.
Prices in USD, excluding tax. Metered overage applies to AI turns, outbound email and voice minutes beyond your plan, and every rate is listed on the pricing page.
An integration that only sends you a notification is not the same thing as one your agent can read and write to. These are ours, grouped by what each one actually does.
One customer layer
Agent + knowledge + inbox
Search existing records, then create a Zendesk ticket or HubSpot contact when the action is allowed. Credentials are encrypted and checked again on every request.
Look up a Shopify order or sync Notion pages into the knowledge base. These provide context; they are not presented as full write connectors.
WhatsApp carries customer messages, Zapier receives outbound webhooks, and Stripe runs billing. Three useful connections, three different jobs.
Something we have not built?
There is a REST API, outbound webhooks with rotated secrets, and SDKs for React Native, Vue, Svelte, Angular, a PWA shell and a web component. Anything reachable over HTTP is reachable.
Every business that contacts us has the same problem. Some of the people reading your site were never going to click Contact, and some were going to buy tonight and find you closed. Popups, email, segments and satisfaction surveys are already here — on the same plan, talking to the same customers as your support desk.
You do not need to choose between handling support and filling a pipeline. It is one product and one price.
See the engagement featuresOffer, announce, or ask one question at the moment someone is reading rather than clicking. Four formats — modal, slide-in, bar, fullscreen — placed in any of seven positions.
Every popup has triggers, variants and per-submission tracking, so you can tell which one actually produced the signup instead of guessing.
Write one email to everyone, or set up a sequence that sends the next one when someone opens, clicks, or buys. Scheduled sends pause and resume without losing the list.
Delivery is tracked per recipient — sent, delivered, opened, clicked, bounced — so a campaign tells you what happened rather than what you hoped.
Group your visitors, subscribers and conversations by whatever matters — what they came from, what they bought, whether the AI handled it or a person did.
Those groups then drive the email and the popups, so the offer lands with people likely to take it instead of the whole list.
When a conversation closes, the customer gets one tap to rate it and a box to say why. A 1 or 2 is flagged to the team rather than buried.
The rating sits on the conversation and rolls into your average, so you can see the difference between the AI resolving something and a human rescuing it.
Welcome a new subscriber, follow up on a conversation that went quiet, send a digest when the day ends, or fire a popup when someone returns to a page they read before.
These run on the same rules engine as your support automations, so one customer record drives what they see and what they are sent.
Views, submissions, sends and clicks sit in the same analytics as your support conversations, filterable down to the individual popup or campaign.
No separate tool and no second login. If the popup did not earn its place on the page, the numbers say so.
If your customers wait for a reply, this is worth your attention. If they are not waiting, you do not need it. Here is what it looks like in the businesses we keep hearing from.
“The phone rings while you are with a patient.”
“You are on a roof when the next call comes in.”
“Client email, WhatsApp and Slack all need an answer.”
“The same setup question arrives for the hundredth time.”
“An enquiry lands at 9pm on a Sunday.”
“Guests ask the same question at every hour.”
Every one of those is the same product, and the price does not change with your headcount. $79 a month for the whole team — no charge per person, per conversation, or per call answered.
See what each plan includesWe would rather show you what the product actually does than print a wall of compliance logos. Every claim here is something you can switch on and check during the trial.
We do not hold SOC 2, HIPAA or GDPR certification badges, because this codebase does not evidence them. If you need a formal security review or a signed data-processing agreement, ask and we will send it in writing.
Questions about how your data is handled? Read the privacy policy or email us and a person will answer.
The one underneath all of them is whether customers will notice it is AI, and whether you will spend forever feeding it. Here is the honest answer to both.
Still deciding? Ask it the question you would be embarrassed to put in a form. It answers from the same documents you would give it, so you are testing the real thing.
Prefer to read first? The guides cover setup, pricing maths and migrations in more depth.
Most teams are live on one channel the same afternoon. You point it at your website or upload the documents you already send customers, write the rules for when to hand off, and switch the channel on. Add the other channels whenever you want. There is no data migration and nothing for your developer to build.
Comparisons, migrations and the operational details that decide whether this kind of tool actually works in a small team.
Connect your site, upload your docs, forward a phone number. The receptionist, the chatbot, and the inbox drafts all start answering from the same source the same afternoon. One price for the whole team, and you can cancel from the dashboard.
© 2026 SupportSiteFlow. Built for support teams that know what they're doing.
