Skip to main content
PAM agents are managed voice and SMS agents that you can use from the API with a stable agentSlug. Use an agent slug when PAM has provided one for a supported use case, such as recall outreach or retention follow-up. Your API key determines attribution, billing, and webhook routing.

Agent Selection

Conversation create requests must include exactly one of:
  • agentSlug — a stable slug for a PAM-managed agent.
  • agentId — a specific agent UUID.
Prefer agentSlug when you use a PAM-managed agent in an external integration.

Available Agents

Dynamic variables

Use dynamicVariables to pass the customer, dealership, vehicle, recall, offer, and scheduling details the selected agent needs. Use the canonical snake_case field names below. Each PAM-managed agent has its own required variables. Values must be strings. PAM uses these public fields to construct internal prompt context and tool variables, such as customer, dealership, scheduling, recall, offer, declined-services, and vehicle-logistics context blocks. Those generated context blocks are internal. They are not accepted as public API fields and are not returned by conversation GET or list endpoints.

Recall agents

Use voice-recall for recall calls and sms-recall for recall SMS conversations. Required dynamic variables for recall agents: Optional recall context:
recall_id must identify a safety recall registered with NHTSA. Send either the NHTSA campaign ID or a manufacturer recall ID.

Retention agents

Use voice-retention for retention calls and sms-retention for retention SMS conversations. Required dynamic variables for retention agents: Optional retention context:

Declined-services agents

Use sms-declined-services for SMS follow-up on services a customer previously declined. Required dynamic variables for declined-services agents: Optional declined-services context:

Scheduling and booking fields

Managed agents can discuss the outreach reason with the required variables above. If the agent should search availability or book an appointment, include the scheduling fields as well.

Phone Numbers

Provide fromNumber on every call or SMS conversation that uses a PAM-managed agent.
For custom agents with a configured phone number, PAM uses the number configured on the agent. If you send fromNumber with that type of agent, it is ignored.

Opening SMS Copy

PAM-managed SMS agents also require welcomeMessage. This is the exact first SMS body sent to the customer.
Generate or select the opening message in your application, then pass the resolved copy when creating the SMS conversation.

Webhook Routing

Webhook delivery is scoped to the organization associated with your API key. When a conversation event fires, PAM routes it using the conversation’s organization, the pinned agent version, and the event type.