Dino ERP is built, sold and supported by TechDino — one-time purchase with full source code.
+91 70936 08698 info@techdino.inBuy Dino ERPA shared mailbox, a WhatsApp inbox, a call log with telephony callbacks and multi-channel notifications — all linked to the customer, supplier, lead, ticket or employee they concern.
Conversations today
Communications in Dino ERP brings e-mail, WhatsApp, call logs, SMS and notifications into the ERP, so each message sits on the customer, supplier, lead, ticket or employee it belongs to. It uses your own SMTP/IMAP, Meta or Twilio, MSG91 and telephony accounts, and is self-hosted with source code.
Last updated · TechDino
Communications & contact center
Connect any SMTP/IMAP mailbox. Replies thread correctly, bounces are flagged and inbound mail links to the right customer, lead, ticket or employee by sender address.
Conversations today
Linked
Kite Retail
Open
Atlas Foods
Call back
Lead
Approved
Utility
Communications & contact center
Run WhatsApp conversations through Meta Cloud API or Twilio as helpdesk tickets, with approved templates outside the 24-hour window and an opt-out list that blocks sends.
Conversations today · activity
Re: Invoice INV-0908
Linked · Kite Retail
WhatsApp · delivery ETA
Open · Atlas Foods
Missed call · +91 98…
Call back · Lead
Template · order shipped
Approved · Utility
Communications & contact center
Log calls with outcome, duration and recording link, or let Twilio, Exotel or any system post signed call records. A call report shows calls per user and missed calls.
Conversations today
What's included
Works across every branch of your company, with role-based access, approvals, attachments, comments and a full audit trail on every record.
In detail
Dino ERP runs a shared mailbox over any SMTP server for sending and any IMAP server for receiving. You can test the connection, set a signature, sync on a schedule or by hand, and work with folders, read and unread state, drafts with attachments and rich-text templates. You can also e-mail any ERP document as a PDF.
Yes. Inbound mail is matched by sender address and linked to a customer, supplier, lead, opportunity, ticket, sales order or employee. Inbound mail can also create or update a helpdesk ticket, so support requests do not stay in an inbox.
You connect either the Meta WhatsApp Cloud API or Twilio WhatsApp, with your own account. Inbound webhooks are signature-verified, and conversations appear as tickets in a WhatsApp inbox and on the related record pages.
You manage templates in Dino ERP, and the editor validates them against Meta’s review rules: UTILITY or MARKETING category, header, body and footer, quick-reply and URL buttons, and samples. Contacts on the opt-out list cannot be messaged. Outside the 24-hour window only approved templates can be sent.
It records and reports calls; it does not place or route them. You log calls against a customer, supplier, lead, opportunity, ticket or employee with direction, outcome (answered, missed, no-answer, busy, failed, voicemail), numbers, start, duration, notes and an HTTPS recording link, and can create a follow-up activity. The call report shows calls per user per day and missed calls.
SMS goes out through MSG91, with DLT sender and template ids, or through Twilio, as a notification channel. Notifications reach users in-app in real time, by e-mail, SMS, WhatsApp using an approved template with opt-outs respected, and browser web push using VAPID keys on your server. Each user sets channels per notification type, admins set defaults, and a delivery log retries failures up to five times with backoff.
On customer, supplier, lead, opportunity, ticket and employee pages, a Communications panel lists calls, e-mails and WhatsApp messages, and lets you log a call or send an e-mail or WhatsApp message in place. A unified timeline beside it merges notes, activities, calls, e-mails, WhatsApp messages and field changes into one history.
FAQ
Yes. Dino ERP connects to accounts you own: Meta WhatsApp Cloud API or Twilio for WhatsApp, MSG91 or Twilio for SMS, and any SMTP/IMAP server for e-mail. Provider fees and approvals, such as Meta template review and Indian DLT registration, are between you and the provider.
No. Dino ERP ingests and reports on call records from your telephony provider through callbacks. It does not dial, route calls, run IVR menus or provide a softphone.
No. Recordings are kept by your telephony provider and Dino ERP stores only an HTTPS link to each one on the call record.
No. Customers who want to chat use WhatsApp, and conversations land in the WhatsApp inbox as tickets.
No. SMS is a notification channel only, with no free-form SMS composer.
Twilio and Exotel have dedicated callbacks. Any other system can post signed JSON using an HMAC-SHA256 signature, and repeated deliveries for the same call id are ignored.
Dino ERP keeps an opt-out list that blocks sends, enforces the 24-hour window and requires approved templates outside it.
Works great with
See Dino ERP in a live demo, then get a one-time quotation for your scope. Hosted on your server, under your brand.