When Chili Piper creates a Salesforce Task (e.g. from a Chat/Concierge flow), there's no way to control which Salesforce record type is applied. Tasks get created with a default/incorrect record type, which breaks downstream assignment rules that key off record type, so leads land unassigned or routed to the wrong team.

Real example from the field: inbound chat tasks started coming in with the wrong record type, and the owning team stopped receiving them entirely until someone noticed.

Chili Piper should let admins define or map the Salesforce Task record type per router or task-creation action, so created tasks carry the correct record type and assignment works as intended.

Without it, any team using record-type-based assignment can't trust Chili Piper task creation and will silently miss inbound.