Email deliverability — landing in the inbox, not in spam
Messages go out through a specialist sending service, with a time limit and network errors retried.
The problem
A reminder email that lands in spam is no use at all. Worse: it creates the illusion that the client was told. You rely on the reminder, they never saw it, and you end up with the very absence the reminder was there to prevent.
Deliverability does not depend on the content of the message but on the sender's reputation. Sending from a badly configured server is classed as spam however much care went into the text — and you will never know, because nothing comes back.
It is a piece of infrastructure in its own right, not a line of code.
How it works in Kagenda
Kagenda does not improvise its sending: messages go through a transactional email service whose trade that is.
- A specialist sending serviceMessages go out over infrastructure built for transactional email, with the sender reputation that comes with it.
- A time limit per sendA send that drags on is cut short rather than blocking the queue behind it.
- Network errors are retriedA passing failure triggers a retry rather than the loss of the message.
- Your identity travels with the messageYour business's name, logo and colours, so that the client recognises the sender at a glance.
Who it helps
Frequently asked questions
Do the emails go out from my own address?
They carry your business's name and visual identity. The technical sending goes through Kagenda's infrastructure, which guarantees a correct configuration without your having to touch your DNS records.
What should I do if a client says they receive nothing?
Have them check their spam folder, check the address on file, then resend the message — to a different address if need be. The calendar also flags failed sends.
Can I send marketing emails with this?
No, this infrastructure is for messages tied to appointments. Promotional sending belongs in another tool and carries different consent obligations.