Connected email extends the AVSBL lead inbox. It is separate from signing into AVSBL and does not import the general mailbox.
6 min readUpdated 8 August 2026By AVSBL
Connected email extends the AVSBL lead inbox. It is separate from signing into AVSBL and does not import the general mailbox.
01
Choose a supported provider
AVSBL currently supports eligible Microsoft 365, Outlook and Zoho Mail accounts for connected website conversations. The AVSBL Microsoft application has completed Microsoft publisher verification, and Zoho Mail connections are available across the supported Zoho data centres.
Gmail connected email is coming soon and is not currently available. Provider eligibility, account plans, regional availability and provider charges remain separate from AVSBL.
Microsoft and Zoho are the supported connected-email options; Gmail remains unavailable.02
Authorise the owned project
Start the connection from the authenticated AVSBL dashboard or builder. Sign in with the provider and approve only the permissions shown for the connected-email feature.
Provider passwords never enter AVSBL. OAuth tokens and encryption keys remain server-side and the connection is bound to the owned AVSBL project.
Provider authorisation begins inside the owned project and credentials remain server protected.03
Reply to matched conversations
Replies sent from AVSBL use the connected business mailbox. AVSBL syncs only messages matched to existing website-enquiry conversations rather than reading unrelated mailbox content.
Microsoft and Zoho reply attachments remain stored with the provider and are fetched on demand for an authenticated owner. Disconnect the integration from AVSBL when it should no longer send or sync replies.
Only messages matched to an existing website conversation sync into AVSBL.