# Turn chats into records with “Chats as ” > In SkedX CRM, Inbox → gear → the card named “Chats as ” (for example Chats as Leads) decides who becomes a record. The switch in its title turns it on. Under The chat, tick each channel (WhatsApp, Instagram, Messenger) and each connected mailbox whose new people are added; an unticked channel still shows its chats on an existing record. Under The record, pick the profile they become. Someone already in the CRM with the same phone or email is never added twice — the chat shows on their record. What crosses: name, phone and email land in the profile’s own fields, the ad and campaign come from Signal; a field the profile’s layout marks Required is tagged, and a chat without that value waits (it is never dropped and never half-created) — the card lists who is waiting with an Add box and Ask in the chat. Ownership needs no setting: whoever the chat is assigned to owns a new record; a person who already has an owner keeps them. “Only some chats? Add a rule” opens rules in place: conditions are the same rows every filter uses (channel, number or mailbox, has a phone, has an email, first message contains, came from an ad, ad headline contains), Match all or any, then the profile; the first matching rule wins and rule zero (everyone from a ticked channel) is read last. Once on, the card shows since when it runs, how many it added in 30 days, the last person added and who is waiting; if it cannot run it says what happened, since when, and one fix. In the chat itself the header shows the person’s name from the CRM, where they are (profile · status) and Open record; Add to appears only when nobody matches. Free-form OK / Template only sits in the reply box beside Send. Product: SkedX CRM · Topic: Inbox · Draft — steps not yet re-verified in the live product So that everyone who writes to you from an ad lands on one record by itself — named, owned, and never twice — without a workflow to build. ## Step 1: Switch it on and tick the channels Go to **Inbox** -> the gear -> **Chats as your profile**. The switch in the title turns it on. Under **The chat**, tick each channel and mailbox whose new people are added — each wears its own mark. Under **The record**, pick the profile they become. People already in the CRM (same phone or email) are never added twice; the chat shows on their record. Open it directly: https://crm.skode.ai/flow-inbox?settings=chats_into_crm ## Step 2: See what crosses, and who waits **What crosses**: name, phone and email each land in the profile field shown; the ad and campaign come from Signal. A field your profile’s layout requires is tagged **Required**: a chat without it waits rather than becoming half a record. A field the layout lets chats skip is tagged **Not for chats**. The line under it says a chat missing a required value waits, and **Change in layout** opens the profile’s layout, where Required is set. ## Step 3: Let chats skip a required field A WhatsApp chat has a phone but no email, so an Email your layout requires would make most chats wait. The layout decides: open **Settings -> Field Editor** for the profile (or **Change in layout** on the card) — the profile’s page opens in **Edit layout**. Point at the field, press its pencil, and with **Required** on, switch on **Not for people added from a chat**, then **Save**. Chats and emails can then add someone without it; forms, imports and people typing a record must still fill it. Open it directly: https://crm.skode.ai/settings/field-editor-v2/leads ## Step 4: Only some chats? Add a rule Click **Only some chats? Add a rule**. Each rule is read top to bottom and the first match wins. Its conditions are the same rows every filter uses — channel, number or mailbox, has a phone or email, first message contains, came from an ad, ad headline contains — with **Match all / any**. **Then add them to** picks the profile. Rule zero, everyone from a ticked channel, is read last. ## Step 5: More options: status, broadcast replies, AI answers, automations Click **More options** under the rules. While it is closed it names any choice that is not the default. **Someone already in the CRM writes again**: **Leave status** (the default) keeps a Paid customer Paid; **Change status** asks **If status is** and **Change to**, for chats and connected mailboxes. **Broadcast replies**: **Stay chats** (the default) or **Become your profile too** — a reply within 72 hours of a WhatsApp campaign counts as a reply to it, and a list you upload for a broadcast is never added. **Bring across Flow’s AI answers**: switch it on and point each question Flow asks in chat at one of the profile’s fields; blanks are filled, never overwritten. **Chats start automations**: off, a message starts no CRM automation — nothing is deleted or paused; this one saves at once. The other three save with **Save**. Open it directly: https://crm.skode.ai/flow-inbox?settings=chats_into_crm ## Step 6: Watch it work, and add who is waiting Once on, the card shows since when it runs, how many it added in 30 days and this week, the last person added (**Open** goes to their record) and how many are waiting (**See them** goes to the list). Each waiting person has a box for the missing value: type it and press **Add**, or **Ask in the chat**. They are also added by themselves the moment the value arrives in the chat. ## Step 7: When it cannot run If chats stop being added, the card says so: how many, since when, and what SkedX was told. The button beside it is the one fix — for example running it as your company’s owner. Each person is added the next time they write. ## Step 8: Open the person from the chat In a chat, the header shows the person’s name from the CRM, where they are — profile · status — and **Open record**. **Add to profile** appears only when nobody matches. **Free-form OK** or **Template only** sits in the reply box, beside Send. ## Common questions ### Does someone who replies to my WhatsApp broadcast become a record? Not by default — a reply within 72 hours of a campaign stays a chat. Open More options and choose Become too to add them like anyone else who writes. People already in the CRM are linked either way, and a list you upload for a broadcast is never added. ### Why is a chat waiting? Your profile’s layout marks a field required (often Email) and the chat has not given it yet. The person waits on the card instead of becoming half a record. They are added the moment the value arrives in the chat, or when someone types it on the waiting row and presses Add. If chats should never wait for that field, tick Not for people added from a chat under Required in the layout. ### Can I change Required on the Chats as card? No — the layout is the one place Required is set, so a field means the same thing everywhere. The card shows what the layout says and links Change in layout; there, under Required, Not for people added from a chat lets chats skip that field. ### Why does the chat header show a name the customer never typed? It is the name on their CRM record, found by the phone or email they wrote from — the name your team typed. With no record it shows the name from the channel, and with none at all the number, written properly. ### Where did Convert to enquiry go? It is now Add to , and it only appears when nobody in the CRM matches the chat. When the person is already in the CRM, the header offers Open record instead, so nobody is added twice. ### Does a mailbox add everyone who emails it? Only a mailbox you tick, and only senders the CRM does not have yet. A mailbox set to show People in the CRM never adds anyone — it only links mail to people you already have. ### Who owns the new record? Whoever the chat is assigned to. If the person already has a record with an owner, that owner keeps them. ### Someone who is already a lead wrote again in a new chat — will they get a second record? No. When a chat or an email comes from a phone number or email address already on a record, it joins that record — whether they come back weeks later, write to another of your numbers, or fill in your Facebook form and then tap through to WhatsApp. Who counts as the same person is your duplicate rule (for example phone and email both, or your own customer number); with no rule set, the phone, then the email. Whether to add them as new is never asked for a chat, and a number saved without the country code still matches. Empty fields are filled from the chat and nothing is overwritten; the owner keeps them and is told they got in touch again. The record’s status stays as it was, unless your company chose otherwise under **More options**. The record’s history says they got in touch again. A different number and email is a different person to the CRM: if the same customer used two, merge the two records. Videos and screenshots © 2026 SkedX, with sample data only. Share and link to them freely; copying the SkedX product or its design is not allowed. Terms: https://skode.ai/terms/ ## Related guides - Set up your Inbox in SkedX CRM: channels, who becomes a record, the side panel, templates: https://skode.ai/help/crm/inbox/connect-your-inbox-in-skode-crm/ - Profiles and your Flow inbox: https://skode.ai/help/crm/profiles/profiles-and-conversations/ - Add a person’s Instagram, LinkedIn and other accounts to a contact: https://skode.ai/help/crm/profiles/add-social-accounts-to-a-contact/ - Connect Meta Lead Ads (Facebook and Instagram): https://skode.ai/help/crm/integrations/connect-facebook-lead-ads/ - Merge two leads that are the same person: https://skode.ai/help/crm/profiles/merge-two-leads-that-are-the-same-person/ Source: https://skode.ai/help/crm/inbox/turn-chats-into-records-with-chats-as-profile/