If you run support
The queue is the job, and the week's story about it is the other job.
Doozy reads the conversations, checks each one against billing, and comes back with the list, the count, or the sheet you asked for. The Monday summary posts itself.
You get back Monday morning, every week.
You 10:31
@Doozy pull every refund request from this week, check each in Stripe, and list the ones we still owe.
Doozy APP 10:32
14 requests, 9 already refunded. The 5 still open are listed with the amount and the conversation.
You 10:31
@Doozy every Monday at 9, post the queue summary here.
Doozy APP 10:32
Scheduled. First one lands Monday at 9:00 in this channel.
What support teams hand over
In a thread, after @Doozy, the way you'd ask a colleague. It answers in that thread, with what it did and where each fact came from.
- Find out why a customer was charged twice, from Stripe and your own database, before you reply.
- List every refund request this week and which ones are still owed.
- Draft the reply to a tricky ticket, from the conversation and what the account shows.
- Post the queue summary every Monday at 9, in the channel you choose.
- Pull every conversation about one bug into a Linear or Jira ticket with the examples attached.
- Turn a week of tickets into a sheet of reasons, counts and the accounts behind them.
The tools support teams connect
Each connects with its own sign-in, no keys to paste, and each tool inside it has a switch. These are the ones this team reaches for first; the full list is on the integrations page.
Safe enough to let near your systems
Doozy works like a teammate, so it doesn't stop to ask. You decide what it can reach.
- Every task runs in its own isolated workspace. Credentials stay outside it.
- Every tool has a switch. Tools that delete or overwrite start off.
- Every action it takes is on the audit log, with who asked and what happened.
- Owners and admins connect tools and choose switches. Members can only look.
More in Security and AI & Data Use.
At Spur, this is what support teams say
"A billing question used to mean a ticket to engineering and a wait. Now I ask in the thread and get the Stripe history, the root cause and a drafted reply back before the customer has replied. The morning queue report runs itself, and it's much easier to see what matters first."
Questions support teams ask first
- Does Doozy reply to customers itself?
- Not unless you turn that on. Out of the box it drafts the reply in your Slack thread for a person to send. A tool that sends a message to a customer is a switch an admin chooses to enable.
- Can it read our help desk and our billing at the same time?
- Yes. One ask can cross Intercom, Stripe and your database, and the answer says which it looked at. That is how it tells you why a customer was charged twice without waiting on engineering.
- Do we need an engineer to set it up?
- No. Add it to Slack, connect your tools from the browser, and mention it in a thread. That's the whole setup.
- What does it cost?
- One price a month for the whole workspace, so everyone in your Slack can ask. 14 days free first, no card. Plans are on the pricing page.
Your next hire is one mention away.
Add Doozy to Slack and hand it the thing that's been waiting on someone all week. It comes back done, and it starts learning how your team works from the first ask.
- 14 days free, no card
- One price for the whole team
- Nothing billed until you pick a plan