This is different from two-way SMS conversations in the dashboard. Use this page for in-call reply checks on a NetSapiens SMS DID.
Prerequisites
- An SMS-enabled DID on NetSapiens routed to the agent’s extension, with a carrier assigned.
- Voip UCAAS connected on the AI agent (steps below).
- NS Check SMS Replies unlocked for the organization in Feature Administration.
- Usually paired with Send SMS on the same agent.
Connect Voip UCAAS
NetSapiens functions only appear after Voip UCAAS is connected on the AI agent.- In the Connect App (AI Agents tile in the NetSapiens portal), open the agent list.
- In the agent’s row, click the Integrations icon (gear).
- Click Voip UCAAS (“Connect to your UCaaS platform for subscriber management.”).
- In Configure Voip UCAAS Integration, fill in:
- API Version — v1 or v2. Start with v1 unless you know your platform supports v2. Chat Notification needs v2.
- Voip UCAAS URL — your platform API host (for example
https://core1.example.com)./ns-api/is added automatically if it’s missing. - Username — a user with Domain Manager or higher access in the agent’s domain.
- Password — leave blank to inherit saved reseller credentials when the form offers that.
- Domain — the domain the AI agent lives in (usually pre-filled).
- Advanced (optional) — Client ID / Client Secret. Leave blank unless your platform needs manually issued OAuth credentials; they’re normally auto-detected.
- Click Connect. The Voip UCAAS tile then shows Connected.
Add the function
- In the agent list, click the agent’s pencil (Edit).
- Under Functions, click Add.
- Expand the Voip UCAAS group (“Functions powered by your UCaaS platform.”). The group shows how many of the 8 functions are already added (for example
1 / 8 added). - Click Add next to Check SMS Replies.
- On the function card, fill in the instruction textbox: “Describe when and how your agent should use this function to check for inbound SMS replies.”
- Click Save Changes. You should see Agent updated successfully!
Example instructions
Tips
- Only messages received during the current call are returned, so older history is not mistaken for a new reply.
- Each message’s text may be shortened (for example to its first 200 characters).
- On API v2, replies can arrive in real time through a platform message subscription, with polling as a backup. On v1, replies are checked through polling only.
- You still need Send SMS (or another way for the caller to know the number) for most reply workflows.
