Tamdot support
Signed-in users can create a support request in Settings. Describe the issue without including passwords, tokens or private email content.
Tamdot turns conversations into cases, appointments and tickets. Every request has a clear next action.
The subject, contact, attachments and expected next action emerge from the conversation.
You can review and change what is detected.
Emails about the same subject form a clear case, even across different mailboxes.
When the link is uncertain, Tamdot does not force a merge.
The Alto case still needs the signed contract. Its timeline keeps the conversation and the task together.
Status, owner and Friday’s follow-up stay in view.
Cases stay on track. Follow-ups and overdue work are visible when they matter.
Tamdot prepares a draft. You choose when to send it in your mail app.
Prepare an appointment proposal using your team’s working hours, leave and available resources.
You confirm the proposal. External calendars are not synchronized.
Agenda checks office hours, leave and resources against the selected teammate’s availability.
Existing appointments stay visible. External calendars are not synchronized.
Jonas Weber · Room 1
The requested Tuesday becomes a precise proposal, linked to its case and the right person.
Tamdot prepares the draft. You review and send it in your mail app.
A proposal is not a confirmed appointment. Your team confirms, reschedules or records the outcome.
The appointment, case and owner stay together.
Ticket Management turns a request for help into a ticket, with the problem’s context and a next action.
The ticket shows urgency and the deadline set by your rules, separately from its status.
Assign the ticket and prepare a reply. A similar reviewed solution can provide a starting point.
Review the conversation, confirm resolution and publish a knowledge article when useful.
Sending an email alone does not mean the problem is resolved.
Customer confirmation reviewed.
Use the latest link, then confirm access with the customer.
See which mailboxes are connected, what is read and why. No permission to send or modify emails.
Connection credentials are encrypted. Read the details of access and data processing.
Connection tokens
AES-256-GCM
Disconnect a mailbox, adjust notifications and inspect the activity log. You choose what is analyzed.
Try the sample controls: they never change a real account.
Mila and Jonas follow the same Alto contract. Connected mailbox conversations and the next action stay together.
Access respects roles and the boundaries of your workspace.
French, English or German: teams use a consistent interface while keeping access to the original message.
The examples in this demonstration stay in English.
From Inbox to Secretary, Agenda or Tickets: find the context, the owner and what comes next.
Available applications depend on your plan’s access.
Signed-in users can create a support request in Settings. Describe the issue without including passwords, tokens or private email content.