Otto keeps a form of address, role and history for every contact in its own local table — no second address book with the provider. Creating, editing and deleting all run through the same approval level as sending mail.
Contents
Docs overviewCalendar · Contacts & limits
A contact lives on your device
Contacts live in their own, local table — not in a second address book at the provider. Otto reads from it for salutation and tone, but never writes into or out of it without approval.
What is on file for a contact
-
Form of address
Formal or first-name terms with this person — followed in every draft.
-
Role
For example customer, supplier, tax office, public authority.
-
History
When contact last happened and how many messages there were.
The three tools
- Search
- By name, company or address — at most the first ten hits, with a note when there are more.
- Create or update
- Deliberately runs on the same approval level as sending, not the lower drafting level — this specifically prevents the two-step trick of first adding an unknown address, then writing to it unchecked.
- Delete
- Final, at the same high approval level as deleting or paying elsewhere — also removes linked emails, cases and memory entries, but leaves mailbox messages themselves untouched.
The hard limits
- Connecting No second address book
- Otto creates no additional account and no address book of its own at the provider.
- Create/update Never silent
- Runs at the same approval level as sending — see above.
- Deleting Final, with cascade
- Takes emails, cases and memory entries for this contact with it — mailbox messages stay untouched.
Known gap
Known gap in this documentation build (as of 25 Sept 2026): a reference to Nextcloud contact syncing exists in the source code, but without its own automated test — so it is not claimed as a capability here.
How it works — the three autonomy levels in detail Back to appointments & travel time