The email autopilot: connect accounts, define rules, understand automatic replies.
The page “Email Autopilot Setup Guide” covers the function identified by this URL. The existing summary is expanded with the actual workflow, prerequisites and known limitations. Email accounts are connected through IMAP and SMTP. OAuth for Gmail or Outlook is not implemented. Automatic sending requires an enabled rule and sufficient AI confidence; sensitive categories require an additional explicit opt-in.
Email accounts are connected through IMAP and SMTP. There is no Gmail or Outlook OAuth flow, so the provider's server settings and credentials are required. Test incoming and outgoing connectivity separately in advance of enabling any automatic reply rule.
Connecting an account does not by itself activate automatic sending. A rule opt-in and a sufficient AI confidence level are required. Sensitive categories need an additional explicit opt-in. These controls must remain visible in the explanation because they prevent uncertain or sensitive messages from being sent automatically.
IMAP failures affect message retrieval, while SMTP failures affect sending. Wrong ports, encryption settings, credentials or provider restrictions may break only one direction. Controlled test messages should use controlled addresses and must not contain real customer information.
Rules needs to be narrowly scoped and clearly named. Confirm that external sending is enabled and review excluded categories in advance of activation. A support case needs to include time, account, direction and error text, but never the mailbox password.
For “Email Autopilot Setup Guide”, the expanded text must remain specific to https://zentor-app.de/en/hilfe/e-mail, use only verified facts and clearly separate tenant self-service from actions performed by Zentor. Any support case is best advised to identify this exact page, the active tenant and the observed step without disclosing credentials.
When using “Email Autopilot Setup Guide”, test one controlled scenario at a time and compare the visible setting, the actual system status and the expected result. If the outcome differs, record the exact time, tenant, channel and unchanged error message. Screenshots and support notes must exclude passwords, tokens and unnecessary personal data so that troubleshooting remains both useful and safe.