The inbox keeps itself up to date
New messages arrive on their own, and setting up a sending domain finally tells you what went wrong.
New messages arrive on their own, and setting up a sending domain finally tells you what went wrong.
The shared queue is meant to be the one place a branch looks. That only works if what is on the screen is what is actually waiting, and until now it was only true for as long as it took someone else to reply.
The queue now updates itself. A text reply, an email, a booking confirmation — each appears in the list as it lands, on every screen that has the list open. Two people in different branches see the same thing without either of them pressing anything, which is the difference between a shared queue and two people guessing whether the other has picked something up.
### Domain setup that explains itself
Verifying a sending domain means putting records in your DNS, and DNS is unforgiving about detail. Previously a wrong record produced one generic failure for every possible cause, and the retry button often did nothing because there was nothing left to retry against.
Both are fixed. The screen names the record that is wrong, and retrying starts a fresh check rather than re-reading the result of the last one.
### One inbound email fix
In an uncommon case an inbound email could be turned away instead of becoming an enquiry. If you have ever had a customer insist they replied to a reminder when no reply reached you, this may be why. It no longer happens.
Talk to us
Tell us your branches, your channels, and roughly how many customers come due each month. If it is not a fit, we will say so.
One business dayOne person, one email. No sequence, no drip, and no calendar link to negotiate with.