Your help articles
The only text it may quote to a customer. Publish an article and it knows it.
customers · sales and support
An AI assistant answers your own customers on your website, help centre, Telegram, Slack, WhatsApp and your own tool. It qualifies buyers, hands refunds and anything uncertain to you with a draft, and a small outbound list goes out from your own Gmail once you approve it.
① on your website
A how-to question is answered from your help articles. A buying question becomes a lead. A refund goes to a person. A bug becomes one reported problem, ready to fix in Studio.
Tally
Receipts by WhatsApp, for bookkeepers.
Your clients send a photo. You get a tidy folder. No more chasing.
What lands in your Inbox
Open the chat bubble and ask something. The result appears here.
② every channel
Wherever a customer writes, the conversation lands in the same Inbox, with the same assistant, the same rules and the same customer record.
Website chat
Visitor on tally.example
Do you work with Xero?
Connected with: One script line on your site
Inbox · one list 1
③ the inbox
Conversations that need a person come first, then by what the customer pays and whether they are past due. Take one over and the assistant stops there; hand it back when you are done.
Customers
Conversations that need a person come first, then by what the customer pays.
🤖 The assistant answers here when it may.
④ outbound, small on purpose
You add the people, each with a reason. The assistant writes a first message and two follow-ups. Nothing is sent by a schedule: a person approves the day’s list, and each message is checked again at the moment it goes.
Inbox · Today
From maya@tally.example through your own Gmail. 4 due today · cap 15 a day.
Your reason Asked about WhatsApp receipts at a meetup
Your reason Runs a 6-person practice; posted about chasing receipts
First message · today
Hi Tom, I’m Maya from Tally. runs a 6-person practice; posted about chasing receipts, so I thought this might help: your clients send receipts by WhatsApp and you get a tidy folder. Worth a look?
Don’t want these? Unsubscribe: tally.example/u/… (always included, cannot be removed)
Your reason Trial ended last month without uploading
Your reason Referred by a current customer
⑤ you set the rules
Checked on the server for every message. Otherwise the customer is told a person will reply, never given the model’s words.
Inbox
One switch, then a choice for each kind of question.
A how-to answer at 0.72 confidence would be sent by the assistant
Also checked for every message: the customer wrote first, nobody has taken the conversation over, the reply repeats no internal material, and the day’s answer limit (300 by default) is not used up.
what it knows
Account details reach the assistant only for a verified customer: one your server signed a token for, one who wrote from that email address, or one sent by your own tool. A visitor who types an email address is not verified.
The only text it may quote to a customer. Publish an article and it knows it.
Read-only, through your GitHub connection, to understand how the product behaves. Never quoted.
With a read-only key: the customer’s plan, status, renewal, recent invoices and failed payments.
That customer’s recent events, errors and sessions, from a project-scoped read key.
Company, role and lifecycle stage from your connected account.
Whole-site traffic and a hint when it drops. Cookieless and aggregate: never about one visitor.
one line on your site
About 6 KB compressed, no dependencies and no cookies. It loads nothing until a visitor opens it. Signed-in customers are recognised when your server signs a short token.
index.html
<script async
src="https://app.seerist.xyz/support/widget.js"
data-seerist-support="sp_…"></script>Your key goes where the dots are. Setup shows it.
where it stops
The assistant cannot refund, cancel, change a plan or give a discount, and it is told never to say it did.
You add the people you write to, each with a reason. Seerist does not buy contacts, look people up or identify anonymous visitors.
Outbound is email from your own mailbox, a small list a day, approved by a person.
The first assistant reply on every channel says so, and every assistant email has a footer. There is no switch for this.
No. It replies only when the customer wrote first, and only on topics you set to answer. Outbound messages are a separate list that a person approves each day, sent from your own mailbox.
The customer gets a fixed line saying a person will reply, never a guess. The conversation arrives in your Inbox with a one-line reason, a summary and, when there is one, a draft for you to edit and send.
No. Refunds, cancellations, legal and security questions cannot be set to answer. The assistant hands them to a person with a draft, and it never says it took an action.
Website chat (one script line), your public help centre, Telegram, Slack, WhatsApp and your own tool through a webhook. Inbound email is coming: it is not switched on yet.
From your own connected Gmail or Google Workspace account, never a Seerist address, to people you added with a reason. Each message is checked at sending: the daily cap (15 by default, 40 at most), country rules (never Germany or Canada), the do-not-contact list, and whether they already replied. Every message has an unsubscribe line that cannot be removed.
Each assistant answer is one AI action from your plan’s allowance. There is no charge per resolution, and a handoff costs nothing extra.
About 6 KB compressed, with no dependencies and no cookies. It requests nothing until a visitor opens it, and stores a random conversation key only after they send a message.
Start free, publish a few help articles and paste one line on your site. You decide what the assistant may answer.