Unified inbox
Threads from supported channels normalize into one list with channel badges, unread state, assigned operators, and delivery state.
Product capabilities
A messaging CRM shaped around service conversations.
Gatelo keeps the center of gravity on the thread: who the customer is, what they need next, what can be sent, and what should be audited later.
- Workflow
- Conversation inbox, customer profile, appointment context, follow-up
- Delivery
- Provider-aware channels with retries, receipts, and audit history
- Consent
- Per-channel consent and opt-out state by design
- AI boundary
- Drafts and suggestions only; a human sends
Build posture
Inbox and customer context
Operators need a fast messenger-like surface, not a heavy helpdesk. Gatelo is built for scanning, replying, merging identities, and seeing appointment-led context next to the thread.
Customer timeline
The customer card can show identities, prior conversations, appointments, notes, service preferences, and follow-ups.
Scheduling-adjacent actions
The product supports reminders, follow-up prompts, appointment notes, and next-action suggestions around service work.
Channels and delivery
Messaging channels differ in templates, windows, media support, receipts, identity, and regional rules. Gatelo's adapter model is designed to surface those differences instead of hiding them.
Adapter capability matrix
Each channel account can expose what it supports: inbound text, media, templates, quick replies, receipts, voice notes, location, and other provider features.
Outbox dispatch
Outbound messages are queued, retried, deduplicated, and reconciled so operators can see whether delivery succeeded or needs attention.
Maturing regional routes
LINE, Zalo, KakaoTalk, WeChat partner routes, RCS, Apple Messages, and other regional channels are treated as staged integrations, not blanket live coverage.
Consent, audit, and administration
Gatelo's trust surface is built into the workflow: consent records, opt-outs, delivery history, role-aware operator visibility, and readable customer data handling.
Consent ledger
Consent and withdrawal state are tracked per customer, channel, and consent type, with enough history to explain why a message was or was not allowed.
Operator visibility
Admin surfaces are planned for channel health, assignment, reconciliation, audit events, and support diagnostics.
Data protection posture
The architecture is designed for tenant isolation, product-scoped data, export/delete workflows, and regional data handling as commercial regions mature.
AI with a clear boundary
AI is useful when it reduces typing and improves context. It is risky when it sends without review. Gatelo keeps the boundary visible.
Draft replies
AI can draft a response using conversation history, customer context, service catalog details, and the operator's selected language.
Suggest next action
The assistant can propose actions such as book, reschedule, follow up, send a price list, or escalate.
Human approval
The product requires a person to review and send. This is a product truth and a platform-safety boundary.
Contact
Product, billing, privacy, or partnership questions
Gatelo is in development. For early-access questions, product fit, billing posture, privacy requests, or partnership inquiries, contact the SOV17 operator inbox.