Skip to main content
POST
cURL

Authorizations

x-api-key
string
header
required

Path Parameters

leadId
string
required

The ID of the lead to switch the customer profile for.

Body

application/json

The new customer profile to switch the lead to.

profile
string
required

The name of the new customer profile to switch the lead to.

sendMessage
boolean

Whether to send the new profile's first message to the lead after switching. Defaults to false. When false, no first message is scheduled for the new profile, so the switch does not automatically initiate contact. With followUps: "restart", the existing pending follow-up (if any) is also canceled. Must be false or omitted when followUps is continue. When true, the first message is scheduled after the delay in messageDelayHours / messageDelayMins below; if both are omitted (or 0), the message is sent immediately, subject only to outreach-hours/holiday adjustment.

messageDelayHours
integer

The number of hours to wait before sending the message. Takes precedence over messageDelayMins.

messageDelayMins
integer

The number of minutes to wait before sending the message. Used as an alternative to messageDelayHours.

clearMemory
boolean

Whether to clear the AI's memory of the existing conversation with the lead. Defaults to false.

followUps
enum<string>
default:restart

What happens to the lead's scheduled messages and follow-up cadence when the profile changes. restart (default) deletes the first-message schedule, cancels all pending scheduled messages except manual ones, and resets the lead to step 1 of the new profile's cadence (follow-ups stop if the new profile has follow-ups disabled). The reset schedules nothing by itself: with sendMessage false the lead has no pending outreach until its next interaction, and with sendMessage true the new profile's first message goes out after the delay and the cadence continues from there. continue keeps AI-scheduled messages (callbacks, call reminders, event reminders), manual messages, follow-ups a user scheduled for a date, and the first-message schedule, and replaces the pending automated follow-up with step 1 of the new profile's cadence, starting now. If one of the kept messages is pending, no automated follow-up is added; the cadence continues from step 1 after it sends. A lead not contacted yet gets its first message under the new profile. Stopped leads and leads in long-term follow-up are left as they are, and only the profile changes. If the new profile has follow-ups disabled, automated follow-ups are canceled and follow-ups stop, even for long-term leads. continue can't be combined with sendMessage: true (returns 400), and an unknown value also returns 400. Use continue to switch a lead after a call without losing a callback the lead booked.

Available options:
restart,
continue

Response

200 - application/json

Customer profile of lead switched successfully.

message
string
sendMessage
boolean
messageDelayHours
integer
messageDelayMins
integer
followUps
enum<string>

The follow-ups mode that was applied.

Available options:
restart,
continue