Contextual answers
Guide service using sources approved for the operation.
SON.IA · Inbound Communication
WhatsApp service with context, rules, and configured handoff.
SON.IA receives requests, checks authorized knowledge, qualifies the need, and routes exceptions to the responsible team according to the configured operational flow.
Do not share personal, confidential, or customer data in public demonstrations.
Fluxo demonstrativo
“Preciso saber se o plano atende o volume da minha equipe.”
SON.IA consulta
Regras comerciais + volumes do catálogo + dependências do plano.
Resposta orientada
Explica a opção compatível com o contexto informado.
Handoff quando necessário
Encaminha escopo, exceção ou decisão ao responsável.
- Authorized knowledge
- Human handoff
- Configurable flows
- Integrations assessed in scope
Companies served by onsmart.AI throughout its history
Consistec e CelerNestléSoftysRadil AlimentosAvivarMetagalTronoxHolambraFresenius KabiGrupoSCNissinColgate-PalmoliveNTKSotreq CATCSI CargoClariosP.S.C.A.RadixCoca-ColaDB DiagnósticoBravo Serviços LogísticosGloboConsistec e CelerNestléSoftysRadil AlimentosAvivarMetagalTronoxHolambraFresenius KabiGrupoSCNissinColgate-PalmoliveNTKSotreq CATCSI CargoClariosP.S.C.A.RadixCoca-ColaDB DiagnósticoBravo Serviços LogísticosGlobo
An observable flow
From message to the next permitted action.
The goal is not to hide complexity behind a generic promise. It is to make clear how a request enters, finds context, and reaches an answer or handoff.
Capabilities, records, and actions vary by plan, channel, consent, data, integration, permissions, and configuration. Scope is validated before contracting.
- 01
The message arrives
The contact enters through the connected channel and is associated with the configured flow.
- 02
Intent is interpreted
The agent uses the knowledge sources authorized for that scenario.
- 03
An answer or action is selected
The next step follows available rules, permissions, integrations, and limits.
- 04
Exceptions go to a person
When the flow requires approval or judgment, the team takes over with the defined context.
What to evaluate in the pilot
Less friction without promising unrestricted autonomy.
Qualification before handoff
Collect the information required by the flow before routing to the team.
Continuity between agent and person
Define when and how a conversation should be transferred.
Configured next action
Connect the conversation to a permitted process step when an integration is available.
A good fit when
- There is repetitive demand for answers or triage
- An authorized knowledge source is available
- The team can define rules, exceptions, and owners
Needs preparation when
- Answers depend on scattered or unauthorized data
- There are no owners for exceptions
- The operation requires integrations that have not been assessed
Entry point
Inbound Communication Essential
An initial reference for inbound operations. Tier selection should consider volume, channels, integrations, and governance.
- 12-month contract
- Monthly or annual billing
- Setup sized in the proposal
- SON.IA Copilot available in every plan
Questions before moving forward
Does SON.IA answer any question?
No. Answers should use authorized knowledge and behavior depends on scenario configuration. Out-of-scope questions can be routed or handled according to the defined rule.
Is human handoff automatic?
Handoff can be configured by intent, rule, limit, or exception. Actual behavior depends on the channel and implemented flow.
Are system integrations required?
Answering from static knowledge may have a simpler scope. Consulting or acting in systems requires assessment of integrations, permissions, and data.
Is setup included in the subscription?
No. Setup is sized according to scope and detailed in the commercial proposal before contracting.
Bring a real flow to the assessment.
Show a frequent conversation, the information source, and the moment when a person must take over. The team can then size the plan, setup, and integrations.
The recommendation is preliminary and does not replace technical, commercial, privacy, and governance validation of the use case.