Emails, texts, and voicemails land in one inbox. Stoke reads each one, drafts the reply in your voice, books the job, sends the reminder, and asks for the review — starting with every draft waiting for your tap.
Stoke isn't another CRM you have to feed. A customer writes in, and by the time the job is done it has drafted every message, made the booking, sent the reminder and asked for the review.
A text at 9pm, an email through your site, a voicemail while you're on a ladder. All three land in the same inbox, transcribed and read.
Who's asking, what they want, when, how many — with the customer's own words kept beside the summary, so you can check what they actually said.
Lead becomes job, calendar event comes with it — right duration, right timezone, linked to the conversation it came from. And a time nobody stated is marked unconfirmed, not invented.
Built off the job's own record, with a payment link on it. After the visit, Stoke asks for the Google review while it's still fresh.
A real drafted reply. It knew the boat was already booked, and it said so before offering another day.
Most software for a small business is a filing cabinet. It stores what you already did. Stoke does the work — then tells you honestly what it did and what's still waiting on you.
Built inside an owner-operated business, where missed inquiries, scheduling, invoicing and content all compete for the same limited hours.
You're holding a boat, a hose, a ladder, or somebody's dog. The microphone sits on every screen in Stoke, so the office work happens out loud while the actual work keeps happening.
Book a job, move one, add a note to a customer, send an invoice, ask what's still unpaid. Stoke shows you what it's about to do, and you confirm.
Confirmations, reminders, and review requests are the difference between a booked job and a no-show, and between a happy customer and a review nobody wrote. They're also the first thing that falls off when you're busy. Stoke sends them on rules, not judgment.
The customer gets it while they still remember writing to you.
Fewer people forget. Fewer trailers get hitched for nobody.
With your Google link in it. The best time to ask is the day it went well — exactly when you're least likely to remember.
By email or text, based on how the customer contacted you. You don't have to think about it, and neither do they.
The worry isn't that AI won't do enough. It's that it'll do something embarrassing to a customer, in your name, and you'll hear about it from them. So the amount Stoke does on its own is a dial you hold, and it starts all the way down.
Every AI-written reply to a customer waits in your queue — nothing goes out until you read it and tap send. Confirmations, reminders and review requests are rule-based and follow the settings you choose separately.
Replies Stoke is confident about go on their own. Anything uncertain still waits for you. You stop reading the easy ones and keep your eyes on the ones that need them.
You set the confidence bar yourself. Above it, Stoke sends. Below it, you decide.
At every setting, including autopilot. A reply that comes back without a confidence score never sends on its own — an agent that doesn't know how confident it is has no business acting alone.
Drag a job to completed and Stoke tells you whether that's about to send the customer a review request — or why it isn't. The consequence shows up before the click, not after.
Stoke records which setting was in force at the moment each decision was made. Turn autopilot on in March and off in June, and the March decisions still show what governed them.
And underneath the dial there are limits that don't move, because the confirmations and reminders run on rules rather than judgment.
Eight to nine, in your timezone, not ours. A shop in California doesn't get its customers texted at 5am because a server in Virginia thought it was mid-morning.
A customer texts STOP and the number is blocked from that moment, with a record of every consent change. If Stoke can't confirm someone is still opted in, it doesn't send.
A review request requires evidence the job actually reached completion. No completed job, no message — and that isn't a setting you can turn off.
Every scheduled follow-up is recorded before it goes out, so the same message can't be sent again through another channel.
Every tool shows you what it accomplished. That's the easy half. Stoke also shows you the number that actually matters — how many people wrote in and are still waiting on you.
On the dashboard every time you open it, and by email Monday morning.
A score for the parts that are slipping, from the last 30 days.
Tap it and you're looking at the people it's counting.
How many leads become jobs, how much follow-up is uncovered, how many jobs have gone cold — shown whether or not it flatters us.
A tool that only reports its wins is a tool you have to double-check, and double-checking is the work you were trying to hand off. A number that can go up when we've dropped something is the only kind worth trusting.
Most social tools hand you an empty box and a calendar and wish you luck. Stoke already knows what you did today, what it was, and which photos came off it — so the draft starts from real work instead of a blank screen.
Photos and video land against the work they came from. Open a finished job, pick the shots you like, and the draft already knows the service, the boat, the yard, the dog — because it's reading the same record the invoice came from.
Posts use the voice you set once. If your customer messages sound like you, so does your feed.
Pick shots from the library and get a short video — captions on the footage, a separate caption for the post, music underneath.
Choose a time and Stoke posts to Facebook and Instagram on its own, without you opening either app. If a window gets missed it doesn't quietly double-post to catch up.
Engagement syncs back into the library, so your photos are ranked by what people actually responded to. Next month's posts start from what worked instead of what you happened to remember.
Made in Stoke. Published to Facebook and Instagram from the Trusty Sail & Paddle account.
The clips were already in the library — shot on a phone, uploaded once, sitting against the rentals they came from. Choosing them was the only real decision.
Stoke wrote the caption in the shop's voice, burned it onto the footage, set the music, and wrote a separate post caption with the hashtags. Then it went on the schedule and published itself.
The engagement it earned came back into the library, so the photos that worked here are the ones that get suggested next time.
Generic software makes you translate. Everything is a "job" and a "customer" and a "quote," even when your trade has perfectly good words of its own. Stoke uses yours. Pick one.
The words change, but so does what Stoke watches for. A pressure washer's inquiry says "driveway" and "mildew" and "how much." A rental shop's says "Saturday," "how many kids," and "do you have four." Different trades, different signals, different questions worth asking back.
A default has to be neutral or empty — never somebody else's vocabulary. Blank is honest. Wrong is not.
Everything you'd expect from the system running your front office — without turning this page into a feature checklist.
Stoke can learn how you write from your own replies, your website, and your social posts, so drafts come back sounding like your business rather than like software. Tell it what to change and it adjusts. Or skip all that and pick professional or casual.
Build an invoice off the job's own record. Stripe payment links on it. QuickBooks sync so your books aren't a second job. And Stoke knows the difference between printing a PDF and actually delivering it to a customer — printing one doesn't mark anything sent.
Multiple users, role-based permissions, assignment.
I'm Andrew. My wife Heather and I own Trusty Sail & Paddle in Morehead City, North Carolina — kayaks and sailboats, rentals and retail. We built it into a million-dollar business and then spent every evening buried in the inquiries it generated.
Stoke runs the front office of that shop. Not a demo of it, not a sandbox — the actual business, every day. I use the same production build you'd be signing up for, with my own customers and my own reputation on the line.
Stoke is young, so I'm not going to pad this page with a logo wall or testimonials I wrote myself. What I can show you is the product running a real business every day, and the person who built it having to live with it on a Saturday in July.
Every core Stoke capability is included at $99. Team adds people, locations, and administrative control. Both start with a 14-day free trial, no credit card.
Your invoices sync to QuickBooks and export as PDFs, so your accounting is never trapped here.
At the default setting you'll see it before your customer does — every reply waits for your tap. When you edit a draft, Stoke keeps a record of what you changed.
You can point it at your website and social posts and let it read how you already write, and it learns from your own replies as you use it. Tell it what to change and it adjusts. If you'd rather not bother, pick professional or casual and move on.
You connect the Gmail inbox you use for customer inquiries — and if your business email lives elsewhere, you can auto-forward it into a Gmail account and connect that. Stoke reads the messages that come into it so it can parse them into leads and draft replies — that's the whole job. Your business is walled off from every other business on the platform; nothing you receive is visible to another account, and nothing is used to train a shared model. You can disconnect the mailbox from Settings at any time, which stops the sync immediately. The details are in our privacy policy.
Stoke gives you one for texting, registered with the carriers so your messages actually deliver instead of getting filtered. Your existing number keeps working.
Stoke includes presets for common service businesses, each with its own vocabulary and timing, plus a neutral setup for anything else. If yours isn't listed it still works — it just won't guess at words it doesn't know.
You probably shouldn't switch for a prettier database. Switch when you're tired of being the person who turns every inquiry into a reply, a booking, a follow-up and an invoice.