FridgedoorAn activity trail on the account
Who did what, and when, kept for as long as your organisation needs it.
Several branches sharing one queue creates a question that does not arise with one: who did that? Who replied to this customer, who changed the wording of the service reminder, who signed in on Sunday.
There is an activity log now, and you can read it. It covers sign-ins and changes to your email and SMS templates, and it is the trail behind the "who said what" the shared queue is supposed to answer.
Retention is measured per organisation, from your own last activity, rather than everyone being trimmed on one clock. A quiet account does not lose its history for being quiet.
### Two things worth stating plainly
The activity log **never records a password**. It records that an authentication happened, not what was typed.
The billing report counts **SMS units, not rows**. A long message is sent as more than one unit and is billed as more than one — the report had been counting messages, which understated what a long reminder actually costs. This is a correction that may make a number go up; it is the true number.
new
- An activity log you can read, covering sign-ins and changes to your email and SMS templates.
- Retention is measured per organisation from your own last activity.
fixed
- The activity log never records a password, and the billing report counts SMS units rather than rows.
Talk to us
See it against your own reminder volume.
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.
- A mapped plan for your locations, domains and templates
- A written quote covering seats, SMS volume and sending domains
- An account set up with your own templates before anyone logs in
One business dayOne person, one email. No sequence, no drip, and no calendar link to negotiate with.