Skip to content

Inbox

Beta

Every client’s texts, emails and chats, one thread per person.

Answer every client’s leads from one inbox, or filter to one client. Replies go from the client’s own number or email address, and each message says in plain words whether it arrived.

What a workflow sent sits in the same thread, labelled with its name, so you pick up the conversation knowing exactly what the lead has already heard.

Thrum opens soon. Sign up now and you’ll be among the first in.

The inbox across clients: a lead's text thread open, with the workflow's first reply labelled and a person's reply after it.The inbox across clients: a lead's text thread open, with the workflow's first reply labelled and a person's reply after it.

Website chat

Beta

Add a chat button to the client’s website, and answer it from the same inbox.

One script tag adds a chat button in the client’s name and colour. Set office hours, a greeting and an away message for each client.

If the visitor leaves before you answer, your reply follows them by email or text, with a link to carry on the chat.

The chat widget open on a phone, in the client's colour, with its greeting.The chat widget open on a phone, in the client's colour, with its greeting.
A website chat in the inbox: a visitor on the boiler-servicing page asks about a service, the reply goes from the inbox, and the thread shows they are on the page now.A website chat in the inbox: a visitor on the boiler-servicing page asks about a service, the reply goes from the inbox, and the thread shows they are on the page now.

The rules it keeps

Opt-outs, quiet hours and bounces, handled for every client.

A lead who texts STOP hears nothing more, from people or workflows, until they text START. Automated texts wait out the night in the client’s time zone, while a person’s reply goes at once.

Automated email carries one-click unsubscribe, and a hard bounce or a spam complaint stops further email to that address, with the reason in the thread.

A thread where the lead texted STOP: the inbox shows they have opted out.A thread where the lead texted STOP: the inbox shows they have opted out.

The client answers too

The client’s team can reply from their phone.

Managers at the client can read and answer their own leads in their portal, and their replies go from the same number or address as yours. You can switch this off for any client.

The client's portal inbox on a phone, in their colour.The client's portal inbox on a phone, in their colour.

Specs

Inbox details

TextsUS and Canadian numbers
On the client’s own Twilio number
Email
From the client’s own verified domain, threaded both ways
Quiet hours for automated texts
21:00 to 08:00, in the client’s time zone
Opt-out wordsSTART, YES or UNSTOP opts back in
STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT
Automated chat replies
At most 5 a chat, from up to 8,000 characters you write
Continue-the-chat link
14 days
Inbox email a month, per seat
Solo 500, Agency 5,000, Scale 25,000

Questions about the inbox

Can a message from a lead start a workflow?

Yes, every message or only a lead’s first. STOP, START and HELP never start one.

Will a retried workflow text the lead twice?

No. A message a workflow sends carries the workflow’s name and links to its run, and a retried run never sends it again.

Can the website chat answer by itself?

If you want it to. An optional first reply is written from notes you provide, on your own OpenAI key, and hands over as soon as a person answers.

Which phone numbers can it text from?

The client’s own Twilio number, in the US or Canada.

What does Beta mean?

Beta means the module is built and tested, and hasn’t yet run against the live service it depends on, such as Stripe or Twilio. The tag comes off once it has.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.