Integrations · Email and SMS
Email, SMS and push integrations in Tezify
The Email card sends from your own address, the Email inbox card reads a paperwork mailbox, Twilio sends texts, and push to the driver app is run by Tezify.
What each card does
| Integration | Who uses it | Status in Tezify |
|---|---|---|
| Carriers and brokers | Sends invoices, rate cons, packets and alerts | |
| Email inbox | Carriers and brokers | Files emailed PODs, BOLs and rate cons, every 10 minutes |
| Twilio | Carriers and brokers | Sends SMS from your number |
| Push notifications | Carriers | Run by Tezify, nothing to enter |
| Quo | Carriers | Recruiting calls become leads |
Recommended order
- Connect Email first. Factoring packets and invoice emails need it.
- Add the Email inbox reader with a mailbox just for paperwork.
- Add Twilio for texts, with A2P 10DLC registered.
- Check push notifications for the driver app.
These cards only send, except the inbox reader, which only reads and marks mail read.
Common questions
Why must email be connected before factoring?
Factoring packets and invoice emails go out from your own company address, so the Email card must be Connected first.
Can the inbox reader use a Microsoft 365 mailbox?
No. Microsoft blocks password sign-in for IMAP. Forward paperwork mail to a Google Workspace or other IMAP mailbox instead.
Does Twilio's Test connection send a text?
No. It only checks the fields are filled in. Use Live test SMS to send a real text to your own phone.
Ready to do it? This lives at /admin/integrations in Tezify.
Related articles
- IntegrationsEmail integration: send from Gmail, Outlook, SMTP or SendGrid
- IntegrationsEmail inbox reader: file PODs and BOLs on the right load
- IntegrationsTwilio integration: SMS alerts from Tezify
- IntegrationsDriver app push notifications: how they are turned on
- IntegrationsQuo integration: recruiting calls become leads
- IntegrationsGmail App Password for SMTP: fix error 535 in Tezify