Support · every channel
Same answers, every week
Returns, passwords, hours, billing — still typed by hand in email and Instagram DMs.
- Instagram DMs
- No deflection
The ops desk for small businesses that still live in email and DMs
Deflect FAQs on your site, escalate messy cases with the full chat, and shortlist hires from resumes — with auditable support runs and evidence-backed hiring decisions.
Built for Build with Gemini XPRIZE · Small Business Services
Widget → ticketClick a tab to switch
Website widget
Customer askYou have 30 days from delivery for unused items in original packaging. Start a return from Orders → Request return.
Refund policy · §2
Escalate to human
Creates a ticket with this transcript
Teams of 5–50 people rarely need a call center. They need fewer repeats, a clean handoff, and a hiring inbox that does not eat the weekend.
This week
12×this week
Mon · founder overload console
30-day returns on unused items in original packaging.
Support · every channel
Returns, passwords, hours, billing — still typed by hand in email and Instagram DMs.
Upload once, deflect on-site, escalate with context. No 50-agent helpdesk rollout.
Step 01
FAQ, refund policy, hours, billing notes — from Notion, PDF, or a plain text file.
Company memory
Knowledge baseDrop FAQ, PDF, or .txt
Notion export works too
FAQ.md
12 KB
refund-policy.pdf
84 KB
store-hours.txt
2 KB
Step 02
Customers ask on-site. Answers stay grounded in your policies — not generic ChatGPT.
Website widget
30 days from delivery for unused items in original packaging.
Refund policy · §2
Step 03
One click creates a ticket with chat history. Review the execution log; fix the FAQ.
Ticket #1042
Execution log
Review log → fix FAQ gap
One clickSee the full path in the live demo
Widget → escalate → execution log — no sign-in required.
Interactive demo
Follow the same path a founder uses in week one: knowledge → widget → escalate → logs → optional hiring.
Step 01
Upload an FAQ, refund policy, or hours doc — or load sample data so answers are grounded in your policies, not generic AI.
Knowledge base
Drop FAQ.md or load sample data
Do this now
Open the command center and click Load sample data if the workspace looks empty.
Tip: Start with password, billing, and returns — the questions that clog email every week.
Support and hiring share the same company memory — because in a small business, it is usually the same person doing both.
Support lane
Built for routine FAQs — billing, returns, hours, passwords — not phone emergencies.
Hiring lane
You still post jobs outside the app. AI advises with evidence; you decide hire or reject.
If you are under ~50 people and still own the inbox, you are the buyer — not enterprise IT.
D2C / Shopify brands
Returns, shipping, and “where is my order?” policy answers on the store site.
Early SaaS teams
Password, billing, and how-to deflection — escalate SSO bugs with context.
Clinics & local services
Hours, insurance basics, membership FAQs while booking stays in your system.
Tutoring & agencies
Parent FAQ plus a hiring inbox when you screen tutors or support hires.
Honest scope beats “90% autonomous support” marketing that SMBs abandon in 30 days.
Realistic first-90-day target on a clean FAQ: about 40–60% deflection of routine questions, with humans handling the rest — and a weekly log review so the knowledge base improves.
Start free while you prove deflection on your FAQ. Upgrade when tickets and hiring shortlists are part of the weekly ops rhythm. No per-resolution surprise fees.
Command center → widget chat → escalate → execution log → optional hiring shortlist. No sign-in required in demo mode.