AI principles.
How Message.com builds and runs AI. Grounded in your knowledge base. Self-hosted on our own GPUs. Never trained on your data. Override-by-default. Turn-offable per channel.
01Grounding over guessing
Our AI is not allowed to make things up. Every answer the AI gives an end user is grounded in the customer's own knowledge base through retrieval-augmented generation (RAG). If the answer is not in the knowledge base, the AI says so and routes to a human. The model is not configured to backfill with plausible-sounding guesses.
We use semantic search over the customer's own content (their site, their docs, their imported PDFs, their previously resolved conversations). The retrieval step is logged, the chunks that were used are kept with the response, and the response is rejected at generation time if it lacks support.
02Self-hosted by default
The real-time AI in our chat, ticket, and phone surfaces runs on GPU hardware we own and operate. Customer conversations are not sent to OpenAI, Anthropic, Google, or any other third-party LLM API for inference on these surfaces.
We use external APIs only for non-real-time or non-user-facing tasks (batch knowledge-base writing, internal tooling), and only when the workload is suitable for that exposure. Where we do use an external provider, it is named in the sub-processors list.
03No training on customer data
We do not train, fine-tune, or otherwise improve any model on your customer conversations, your knowledge base content, your tickets, your call transcripts, or anything else you store with us. Your data trains nothing.
We train evaluation harnesses (held-out QA sets, regression suites) only on synthetic data or on data we have explicit, written authorization to use, and we never co-mingle one customer's data with another's. This is contractual in the Data Processing Addendum.
04Explainability
Knowledge-backed responses use relevant source material when available. Source links and retrieval details vary by workflow; not every response carries a citation. Review the underlying content when accuracy matters.
Available logs and conversation records can help investigate a response or handoff. They are not a complete record of a model’s internal reasoning, and retention depends on the service and workspace configuration.
05Override-by-default
Agents can review and edit drafts before sending. Configured automation may send replies or perform allowed actions without a manual send step. A delivered message cannot be recalled merely by changing or deleting its audit record; external actions may also be irreversible.
Choose the allowed tasks, source information and handoff behavior for each enabled workflow. Test those settings before allowing AI to act with customers.
06Bias monitoring
Evaluate the assistant with representative questions, language patterns and support needs before rollout. A successful test on one set of examples does not establish equal performance for every customer or situation.
This page does not provide an independent bias certification or a published model-evaluation report. Contact us for available evaluation evidence relevant to your intended use.
07Safety filters
The AI refuses to generate hate speech, sexual content, harassment, content sexualising minors, instructions for violence or weapons of mass destruction, and self-harm content. Refusals are explicit and routed to a human. Refusals are logged so that customers can audit them.
Self-harm and crisis content trigger an additional behavior: the AI returns a brief, calm message pointing to appropriate local resources (where configured) and immediately escalates to a human. The AI is not a crisis counsellor and is never positioned as one.
08Voice cloning consent
Voice cloning is a free feature of our phone product. A 15-second sample is enough to clone a brand voice for receptionist and wait-time concierge use. We require explicit, attested authorization from the brand owner whose voice is being cloned, captured at the moment of upload, before a clone is created.
We never clone an end-user's voice, even with consent, and we never use a cloned voice to impersonate a specific individual outside of the brand-owner-authorized use case. Cloned voices are tied to the customer's workspace and are destroyed when the workspace is deleted.
09Sustainability
We operate our AI inference infrastructure and consider efficiency when selecting and running the hardware. We do not publish an independently verified carbon or energy report on this page.
We will be honest about the number. AI is not free of cost to the planet. The point of measuring it is to keep it small and to give customers a defensible footprint to share with their own ESG team.
10Open-weight preference
We prefer open-weight models with permissive licenses over closed-API providers for our customer-facing AI surfaces. Open weights mean we can host them ourselves, audit them, fine-tune them when policy demands it, and keep the inference cost predictable for the long term.
Today our primary chat, ticket, and phone AI runs on an open-weight model on GPU hardware we own, with no third-party LLM API in the inference path. We review our primary model at least once a year and remain on open-weight unless a non-open model offers a capability gap we cannot otherwise close.
11Customer control
Every AI feature is opt-in and configurable per workspace and per channel. You can disable AI for the chat channel, leave it on for tickets, and turn it off entirely for phone calls if that is what your customers expect. You can set keyword blocks, topic blocks, and language allowlists. You can require a human handoff for any AI conversation that crosses a threshold you define.
See the AI Code of Conduct for the rules that govern how the AI behaves inside those controls and the Data Processing Addendum for the contract that backs them.
Questions about how the AI works?
Email [email protected] or read the AI Code of Conduct. We are happy to walk security and procurement teams through the architecture in detail.
Start free trial →