Skip to main content
A partner rep types one sentence in your shared channel and a registered, attributed deal lands in your CRM. The part worth understanding before you tell partners to work this way is what happens in between, because the agent does not shortcut your qualification.

​
What you’ll achieve

Confidence that a deal registered from chat is the same quality as one registered through your portal form: same fields, same required values, same dropdown options, same validation, and the same downstream automations and approval gates.

​
Before you start

1

Chat is connected and the channel is mapped to the partner

The agent works out which partner it is talking to from the channel it is in, so the shared channel has to be mapped to that partner on your side. Without the mapping there is no partner context and the agent cannot act. See Configure Slack or Teams for partner activity.
2

The partner support agent is enabled

The in-channel agent is the same agent. See Partner Support.
3

A form exists for what you want partners to submit

The agent submits your forms, it does not invent a schema. Whatever you have attached to your portal is what it can offer: deal registration, lead sharing, MDF requests, onboarding, and anything else you have configured.

​
What the rep does

In the shared channel, the rep mentions the agent and says what they want, in their own words and their own language:
That is the whole interface. There is no command syntax and no form to open.
A partner rep registering a deal in one sentence in the shared Slack channel, with the Introw agent confirming the registered deal in the thread and posting the submitted form in the channel.

​
What the agent does with it

1

Picks the right form

The agent matches the request against the forms you have attached to that partner’s portal, whether they are reachable through a CTA, a shared pipeline, or anywhere else in the experience. If you have several plausible forms, it resolves which one the request means rather than defaulting to the first.
2

Reads that form's real fields

It pulls the actual field definitions: labels, types, which are required, and the permitted dropdown options. Your qualification questions are its checklist.
3

Extracts what the rep already said

It maps the sentence onto those fields and normalizes the values: “$20k” becomes 20000, “end of month” becomes a date, and a dropdown answer is matched to one of your real option labels. Partner fields are prefilled from the channel’s partner context.
4

Asks for the rest, in the thread

Anything required and still missing, or provided in a form that fails validation, comes back as a follow-up question in the same thread. The rep answers in chat. Nothing is guessed and nothing is left blank.
5

Submits only when it validates

The data is validated against the same schema your portal form uses. Until it passes, the agent keeps asking. Once it passes, it submits.
6

Hands off to your rules

From there it is an ordinary submission: your conflict checks, duplicate handling, approval gates, notifications, and CRM automations all run exactly as they do for a portal submission. Registering from chat changes the entry point, not the process.
The rep always has an escape hatch. Every exchange includes a button to open the real form and finish it manually, so a rep who would rather click than type never gets trapped in a conversation.

​
What the agent cannot collect in chat

Four field types need the real form, and the agent will say so and hand over the link rather than attempt them: If a required field on your registration form is one of these, chat registration for that form will always end in a handoff to the form. Worth knowing before you tell a partner “just ask in Slack”: if you want chat to complete end to end, keep those field types off the forms you expect partners to submit conversationally.

​
The same thing on WhatsApp

WhatsApp behaves identically once it is set up, with one difference in how the agent knows who it is talking to: there is no channel to map, so the sender is matched on the phone number of their contact record in your CRM. A rep whose contact has no phone number, or a different one, will not be recognized. See Set up WhatsApp.

​
Verify it worked

Ask the agent to register something from a mapped test channel, deliberately leaving out a required field. It should come back asking for exactly that field, by its label from your form, and refuse to submit until you answer. Then check the submission in Introw and confirm your normal approval and automation path ran.

​
Troubleshooting

  • The agent does not respond - the partner support agent is not enabled, or the channel is not mapped to a partner.
  • It offers the wrong form - several similar forms are attached to that portal; make their names and purposes distinguishable.
  • It always ends with “open the form” - a required field on that form is one of the four types above.
  • It says it cannot find a form - nothing matching is attached to that partner’s experience.
  • WhatsApp does not recognize a rep - their CRM contact has no matching phone number.

Set up WhatsApp

Turn on the WhatsApp number partners text.

Ways to register a deal

Every entry point partners can register through.

Partner Support Agent

The agent that answers and acts in the channel.

Slack & Teams

Connect the workspace and map channels.