Inbound

Inbound is where you decide what happens to the leads each source and chat channel brings in: the welcome flow, the Gene AI switch, the AI context and who gets the lead. It is the first item in the Flows left menu (Flows > Inbound).

Once a source is connected, new leads from it land in Gene on their own, get assigned, and get an automatic AI first reply (on by default per source).

Note

Connecting a new source is not done here. It is a one-time job under Settings > Lead Sources, on the tab named after the source (Website, Meta Ads, Webhooks and so on). See Lead Sources. The Connect a source in Settings link at the top of this page takes you there.

Overview#

The page is a list of rows, one per kind of source or channel:

• Meta Ads
• Website
• the chat channels: WhatsApp, Email, Messenger, Instagram and Telegram
• Webhooks
• Portals, where enabled
• Imports, once you have imported contacts
• QR codes, where QR codes are turned on for your workspace

The QR codes row is the last one. It says how many codes you have and how many leads they brought in this month (with no codes yet it is grey and reads "No codes yet", with a Create link). Clicking it does not open a list below it: it opens the QR codes page, where each code has its own scans and leads.

Each source row says how many forms, connections or imports it holds and how many leads came in this month. Only sources that can actually receive a lead are counted: a Meta Ads tick from onboarding that was never finished is listed inside the row with its own Not connected badge, but not counted.

A Meta Ads, Website, Portals or Webhooks row with nothing live behind it is greyed out, says Not connected, and has a Connect link to its tab under Settings > Lead Sources, the same way as a chat channel that is not connected (see Connector rows).

1. Click a row to open its individual sources below it.
2. Click a source to open its editor.

Who each new lead is assigned to is set by the team rotation pool on Routing, the next item in the Flows left menu (see Routing). Each source, and the WhatsApp, Messenger and Instagram channels, can override it with its own Lead routing select.

Chat channels#

Direct WhatsApp messages, emails to your inbox, Facebook Messenger DMs, Instagram DMs and Telegram messages are not lead sources here. They flow straight into the inbox. A welcome message is sent on the channel the lead arrived on.

A chat channel your workspace has not connected yet is greyed out, says Not connected, and has a Connect link instead of opening. The link goes to that channel's tab under Settings > Communication (WhatsApp, Email, Messenger, Instagram or Telegram), where you connect it. Once it is connected, the row opens like the others.

Email counts as connected when mail can come in: a connected Gmail or Outlook inbox, or a domain under Connect your domain on the Email tab whose card shows Receiving as set up (mail to that address has arrived in Gene App). A domain that is only verified for sending (Receiving: not set up yet) leaves the row greyed out; finish the receiving steps on that card. Outreach mailboxes and a sending domain never count. The connected Email row shows the address it uses. A Gmail or Outlook inbox that needs a reconnect does not count, so without a receiving domain the row stays greyed out until you reconnect it.

Each connected chat channel has its own Gene AI switch when you open its row, for example Gene AI replies on WhatsApp or Gene AI replies on Email.

• It turns Gene's replies on or off for that one channel. Every other channel keeps its own switch.
• For one WhatsApp number only, use Gene replies on this number on that number's card in Settings > Communication > WhatsApp (see Gene replies on this number). Gene keeps answering on your other numbers.
• Imported and synced contacts are never messaged first. Only people who reach out get a reply.
• For Email and Telegram, that switch is all the row holds.
• Gene AI is on by default in every workspace, so every channel's switch is on as soon as the channel is connected.
• If someone in your workspace switched Gene AI off for the whole workspace, every channel's switch shows off. Switching one on makes Gene live on that channel only; the other channels stay off until you switch them on.

Lead routing on a chat channel#

WhatsApp, Messenger and Instagram also each have their own Lead routing select:

• Default: the team rotation on Routing.
• Rotate between agents
• Split by percentage
• Always the same agent

Every channel is on Default until someone picks something else. Picking Default again clears the channel's own rule.

On Default, the panel shows who is in the rotation, with each person's weight and working hours (for example "09:00-17:00 · Mon-Fri", or "Hours not set"). An Edit routing pool link goes to Routing.

A channel's own routing rule is set and shown only in that channel's row. It is never listed as a source under Webhooks.

Where leads come from#

Live today:

• Meta lead ads: Facebook and Instagram lead ads through the native Meta integration. You connect your Page, and new form submissions arrive in real time over the Meta leadgen webhook.
• Meta lead ads via Zapier or Make: An alternative Meta path that needs no Facebook login (see below).
• Website: One section for everything your site feeds in (see Website forms).
• Webhooks: A URL that anything can POST leads to: a form builder, an ad platform, Zapier, Make, or your own backend. See Lead webhook.
• CSV import: A spreadsheet or a Meta Ads export, mapped column by column.
• Manual entry: Contacts you add yourself.

Some sources are only shown when Gene Support turns them on for your workspace, so they are off by default: JamesEdition and property portals (Zillow, Idealista, ImmobilienScout24, and others). CloudTalk works for every workspace and is connected under Settings > Communication: once it is connected, someone new who rings your team becomes a contact with the source CloudTalk call (see CloudTalk). Settings > Lead Sources and the rows on this page only show the sources turned on for you, so what you see depends on your workspace.

Give Gene access to your Meta leads#

A Facebook Page can limit which people and which CRMs may read its leads. Once it does, Gene is blocked until it is added, even if you are an admin of the Page. The form step of the Meta connect then says "Meta is blocking Gene from this Page's leads", and a source that was already connected shows Leads access missing.

Only someone with full control of the Business that owns the Page can change this. If an agency runs your ads from its own Business, that is the agency.

1. Open Meta Business Suite and go to Settings.
2. Under Integrations, open Leads access.
3. Pick the Page.
4. On the CRMs tab, add Gene.
5. On the People tab, add the person who connects Meta in Gene App.
6. Back in Gene App, connect Meta again and pick the Page.

If nobody can change it in time, the Zapier or Make path below works without it.

Meta lead ads via Zapier or Make#

You connect your Facebook Page to Zapier or Make (both have a ready Facebook Lead Ads trigger). Then you point their webhook action at the connection link Gene gives you, and leads flow straight into the same Meta source.

It is useful when the native connection is not available yet. Any tool that can POST JSON works.

To connect it (from Settings > Lead Sources > Meta Ads):

1. Name the source, and Gene gives you a connection link.
2. In Zapier, add a Facebook Lead Ads trigger and a Webhooks by Zapier, POST action pointing at that link, with Payload Type JSON and Data left empty. In Make, use HTTP, Make a request with a JSON body that holds every question of the form, not only name, email and phone.
3. Send one test lead to confirm, then publish.

With Data left empty, Zapier sends the whole lead: name, email, phone, every answer to the form's questions, and the campaign, ad and form it came from.

• Gene reads the name, email and phone itself, and the campaign, ad and form show as the lead's source.
• Budget, timeline and motive answers fill those fields on the contact, in any language the form asks them. Every other answer is kept on the contact under its question.
• A source whose leads arrive with only a name, email and phone shows Check setup: the Zap is sending only the fields someone typed in, so the form's answers stay behind in Zapier. Clearing Data in the POST step fixes it from the next lead on.

Website forms#

The tracking snippet is a script tag you paste once, just before the closing </body> tag. On WordPress you can use the plugin instead, which needs no pasting.

• It records page views and form fills, and form submissions become contacts automatically.
• Every form on the site is picked up by the one script, so a site with twenty forms needs no per-form wiring.
• On WordPress, the plugin also sends every Gravity Forms, Elementor Pro, Contact Form 7 and WPForms entry from your site's own server. A lead still arrives when the visitor's browser blocks the script (an ad blocker, a privacy browser, a cookie tool).
• When both copies of one submission arrive, Gene App pairs them into one lead.
• For a form you cannot put the snippet on, create a webhook and point the form's POST at it.
• Each form the script or a webhook sees shows up under the Website row on Inbound, with its leads.

The Website source is shown under your site's domain (for example nimani.com) once the script has seen a form there, unless you gave it a name of your own. When one tracking ID covers several sites, every site is listed under the source, each with its forms and its leads this month; a site whose plugin has not checked in for 48 hours says Plugin quiet 48h+.

Each discovered form#

As each form is discovered, it appears under the Website source. There you can give it its own welcome messages and AI context, switch capture off for that one form, or have it email your latest newsletter to each new sign-up.

Each row identifies the form by:

• its name, taken from the form's own heading, its label, or its submit button. When the only name on offer is an error page's title (a site that shows its contact form on its "404 Not found" page, say), the form is named after its page instead: Form on the home page or Form on /contact. A real heading seen later replaces it.
• the first few questions it asks
• the page it lives on
• when it last brought in a lead

If Gene App names a form badly, use Rename: type the new name in place and press Enter or click away to keep it, or Esc to leave the old one. A name you type is never overwritten.

Open a row to see every question the form asks and to set capture or the first message for that one form.

Forms show up as soon as someone visits a page they are on, so a form can be set up before it has ever been filled in. A row with no detail yet says so rather than looking empty.

Before the first form arrives#

Until the first form comes in, opening the Website row says how forms get there: the snippet, a form webhook, or both, depending on what your workspace has. Or it says the snippet is already live and waiting for a form. It links to Settings > Lead Sources > Website, where both are set up.

What you can do#

• Source row: One per kind of source or channel. Shows the connection count and leads this month. A red warning triangle appears if any source under it has an error. Click to open its list.
• Connect (row not connected): On a greyed-out row. Opens that row's tab in Settings: the channel's own tab under Communication for WhatsApp, Email, Messenger, Instagram or Telegram, and under Lead Sources Meta Ads for Meta Ads, Website for Website, and Webhooks for Webhooks and Portals.
• Connect a source in Settings: Top-right link to Settings > Lead Sources, where new sources are connected.
• Gene AI switch (per source): On by default. Off stops the automatic AI welcome for new leads from that source. Updates immediately, rolls back if it fails.
• Generate AI context (per source): Appears only on Meta and Instagram sources that have no AI context yet. Runs a vision analysis of the ad creative to write the per-source instructions. Reads "Analyzing..." while it runs.
• Open a source: Click a source row to open its editor, with Settings, Welcome flow, Field mapping (webhook and ad-platform sources) and Leads tabs. Every control in it is listed under Details.

Popups and drawers#

• Source editor drawer: Opened by clicking a source row. Its Settings, Field mapping and Leads tabs are described under Details below. Its Welcome flow tab, the automatic first reply and any follow-up steps, is covered on Nurturing.
• Connect flows: Opened from the tabs of Settings > Lead Sources, not from this page. Each one (Meta Lead Ads, Webhook, CSV import and the rest) is described under Add Source, and the no-login Meta path under Meta lead ads via Zapier or Make.

Tips#

• The Gene AI switch on the list is the fast toggle. The Welcome flow tab in the editor is where you write what that reply says.
• For Meta sources, use the per-campaign context blocks for offer-specific instructions and the general context for things true of every campaign on the Page.
• A source showing an error triangle usually means Meta access lapsed. The line under its name says the exact fix.
• A Meta source showing Check setup is receiving leads without their form answers. See Meta lead ads via Zapier or Make.

---

Details#

Everything on the Inbound screen and in the source editor, for when you need to look something up. Lead sources are folded into Inbound, which has no sub-tabs. Where QR codes are on, they are a row in the Inbound list that opens their own page; Inbound stays highlighted in the left menu while you are on it. Routing is its own item in the Flows left menu, not a tab here.

Only live, default-on screens are described in full. Connectors that Gene Support turns on per workspace are noted where relevant but not described in full.

Inbound, Sources view#

Connected lead sources, grouped into full-width rows by connector type. New leads land here automatically and Gene sends the first message (Gene AI, on by default per source).

Connector rows#

There is one full-width row per connector type that is turned on for your workspace, or that already has sources behind it.

• Each row shows an icon, the label, a connection count, and leads this month (contacts imported, on Imports). The count only includes sources that can receive a lead. There is no description line under a row: it shows only its status.
• A row with nothing connected behind it is greyed out with Not connected and a Connect link, and does not open. The rule per row is below.
• The chat channel rows (WhatsApp, Email, Messenger, Instagram, Telegram) show only their name; a connected Email row also shows its address.
• A red warning triangle appears if any source under the row has an error.
• Click a row to open its list below it. Click again to close it.

The rows:

• Meta Ads: Lead ads from Meta campaigns, including Instagram lead ads. Live.
• Website: Visitors and form leads from your site, captured by the snippet or a form webhook. See Website row.
• WhatsApp, Email, Messenger, Instagram, Telegram: Leads who message your number, inbox, Page or account directly. See Chat channel rows.
• Portals: Zillow and other property portals. Off by default; Gene Support turns it on.
• Webhooks: A URL that anything can POST leads to. See Webhooks row.
• Imports: Contacts brought in once from a CSV or another CRM. See Imports row.
• QR codes: Codes for flyers, sign boards and brochures, where QR codes are turned on. Shows the number of codes and their leads this month, and opens the QR codes page instead of a list below it.

Website row#

• Its count is the forms the snippet found. With the script live and no form seen yet, it reads Script live.
• It counts as connected once a live form or webhook source sits under it, or once the Gene snippet or the WordPress plugin has reported in from your site, even before it has seen a form. Until then it is greyed out with Not connected, and Connect opens Settings > Lead Sources > Website.
• Opened with no forms yet, it shows the short empty state described in Before the first form arrives.
• The empty state links to Settings > Lead Sources > Website: Set up your website in Settings, or Website settings once the snippet is live.

Chat channel rows#

The rows come in the same order as the Settings > Communication tabs. They are not backed by lead sources. A channel the workspace has not connected is greyed out with Not connected and a Connect link, and does not open (see Chat channels).

Connected means the same as the channel's Settings card:

• WhatsApp: any WhatsApp number (QR, Meta, 360dialog or Twilio).
• Email: a connected Gmail or Outlook inbox, a domain under Connect your domain on the Email tab whose Receiving is set up (mail sent to that address has arrived in Gene App). A domain verified only for sending, an outreach mailbox, or an older receive-only mail address that has no card on the Email tab does not count: this row is about leads who email you, so it stays greyed out until receiving works (see Receiving on your own address). A Gmail or Outlook inbox that is waiting on a reconnect does not count until it is reconnected. A connected Email row shows its address: the connected inbox, or otherwise the address mail goes out as from your domain (for example [email protected]).
• Messenger and Instagram: a Facebook Page or Instagram account through Meta, Unipile or Sinch.
• Telegram: a Telegram bot or a teammate's linked Telegram account.

What opens:

• A connected WhatsApp, Messenger or Instagram row shows that channel's Gene AI switch and its lead routing. WhatsApp also shows Capture leads, which is always on: anyone new who texts your WhatsApp becomes a lead in your inbox.
• Email and Telegram show only the Gene AI replies on Email / Gene AI replies on Telegram switch, with no lead routing.

Meta Ads row#

It counts as connected once a Meta source can receive a lead: a connected Page or lead form, or a Zapier or Make bridge with its connection link. A source that has ever received a lead also counts. Until then it is greyed out with Not connected, and Connect opens Settings > Lead Sources > Meta Ads.

Webhooks row#

It also holds any other active source type that has no row of its own.

It counts as connected once one of its webhooks has its connection link or has received a lead. Until then it is greyed out with Not connected, and Connect opens Settings > Lead Sources > Webhooks.

Portals row#

Shown only where property portals are turned on. Like Webhooks, it is greyed out with Not connected until a portal source can receive a lead, and Connect opens Settings > Lead Sources > Webhooks, where portals are set up.

A chat channel's own Lead routing rule (the WhatsApp, Messenger and Instagram rules, and the retired cross-channel "Chat leads" rule) is never listed or counted here. A channel's routing is set in that channel's own row.

Imports row#

• It appears only when the workspace has an import with something behind it.
• Each import is listed under it with its file name, the day it ran and how many contacts it created.
• An import with no recorded run and no contacts is not shown at all.
• The Gene AI switch on an import row does not touch contacts already imported. It decides whether Gene greets the contacts the next import adds to that list, and a new import arrives with it off.

Source row (inside an open row)#

• Source name and a status badge: Active, Paused (Capture leads is off), Not connected, Needs attention (the source has an error), Check setup (leads arrive but something about them is incomplete, such as a Zapier bridge that sends no form answers), or Imported.
• If the source has an error: a red line with the problem and the suggested fix.
• Else, if it shows Check setup: an amber line with the problem and the fix, for example "Form answers not coming through" and how to clear Data in the Zap's POST step.
• Else, if AI context is set: a sparkle line showing the first line of the context.
• Else: an "N this month" lead count.
• Generate AI context button: only on Meta or Instagram rows with no AI context. Reads "Analyzing..." while running. Analyzes the ad creative and saves the result as the AI context.
• Gene AI switch: on by default (on unless someone switched it off). Updates immediately and rolls back if it fails. Toast "Gene AI on" / "Gene AI off".
• Clicking the row opens the source editor.

Add Source#

New sources are connected from Settings > Lead Sources, one tab per lead source, not from Inbound. The Connect a source in Settings link at the top right of Inbound goes there. Each tab runs the Add a lead source flow, opened straight on the right connector. When Meta is the only enabled ad connector, its card opens the Facebook popup directly (a one-click Meta Ads connect).

The Add a lead source modal shows a card per enabled connector, each named after the thing it connects:

The Website card's snippet half is a Website tracking card. Its Open the Website tab link goes to Settings > Lead Sources > Website, the only place the script itself is shown.

With no connectors turned on, the modal says "No lead sources are enabled yet." Gene support turns them on per workspace.

Ad platforms flow#

A grid of the ad platforms turned on for your workspace. When Meta is the only one, the picker is skipped.

• Meta Lead Ads:
  1. Log in with Facebook.
  2. Pick a Facebook Page. Greyed-out Pages note "needs Leads access", and a line under the list says who has to allow Gene, with a Show me how link to the steps.
  3. Check the forms to subscribe to ("(N selected)"). Connect stays disabled until at least one is checked. When the Page's Leads access settings block Gene, a red line says "Meta is blocking Gene from this Page's leads" with a Show me how link to the steps.
  4. Choose the connection scope: Whole workspace (default) or Just me.
  • On connect, a one-time vision analysis seeds the AI context (toast "Analyzing ad creative...").
  • The source is named Meta - <Page name>.
• Instagram Lead Ads: Same as Meta, but only lists Instagram-linked Pages. The source is named Instagram - <username>. It is turned on together with Meta.

The no-login Meta path is under Meta lead ads via Zapier or Make.

Forms#

There is no form to build from Add Source. Lead forms are built under Flows > Forms (when Forms is turned on for your workspace), where each form gets its link, script embed and iframe on its Share tab.

Every form makes a source of its own, listed in the Website row. The form publishes, pauses and shares it (see Sources made by a form).

Property portals flow#

Turned on per workspace by Gene Support.

• A preset picker, grouped by region: Zillow Premier Agent, Realtor.com, Idealista, Immoweb, ImmobilienScout24, Other portal.
• Each preset shows connection instructions and a copyable webhook URL (/api/webhooks/inbound/<token>).
• Each preset comes with its field mappings already filled in.

CSV import flow#

Three steps: drop, map, assign.

1. Drop a .csv (max 5,000 rows, header row required).
2. Map each column to a Gene field, with a "<N> of <M> mapped" readout.
3. Assign owners (see Assign step).

Import requires at least one mapped column and at least one column mapped to Email or Phone.

After-import choice#

• Just add them as contacts (default): "Recommended. Gene AI stays off for this import and nobody is messaged."
• Write an outreach for this import: says how many rows can be reached and on which channel. It warns when some of them would get a first WhatsApp message from a number they never wrote to.

The second choice does not fire the source's welcome flow. After the import, it opens an outreach on Flows > Outbound for exactly those contacts (see Outreach for one import). Nothing is sent until you start it there.

Both options point at Flows > Outbound for reaching the list later.

Assign step#

The assign step is one panel:

• which column names each lead's owner
• a row per owner: keep them, invite them, or round robin
• the pool that catches everything the rows leave over
• a running count of where the file lands
• Followers: teammates who see every contact the import creates. This is how an External Partner, such as the developer who provided the database, gets access to exactly those leads and nothing else.

Who else can see the contacts is a separate picker under it.

Progress and the final summary (new contacts, duplicates, skipped, errors) appear on a card in the bottom-right corner, not in the dialog.

Webhook flow#

A four-step wizard: Name, Test payload, Field mapping, Publish. You name the connection, get the link, send one test submission, map its fields, then publish. The source stays paused until you publish it; Publish makes it active. The fields a webhook accepts and what comes back are on Lead webhook.

Source editor, Settings tab#

The source editor opens when you click a source row. The header shows the source name and its source type in plain words.

Tabs: Settings, Welcome flow (not on a one-off import; see Nurturing), Field mapping (sources that map fields) and Leads.

The Settings tab, top to bottom:

• Not published yet (a source whose setup was never finished): leads sent to it are stored so you can check the field mapping, but no contact is created and nothing is sent. Publish starts accepting real leads. It takes effect at once and confirms "Published"; if it fails, the source stays unpublished and a message says why.
• This source belongs to the form ... (a source made by a form in Flows > Forms): see Sources made by a form.
• Capture leads: Switch. "Bring new leads from this source into Gene." Off, new leads from it are not taken in, and the source's badge reads Paused.
  • On a Meta or Instagram source whose Page was disconnected in Settings > Lead Sources > Meta Ads, turning it back on is refused with "This Meta Page was disconnected. Connect it again in Settings, Lead Sources, Meta Ads." Connecting the Page again makes a new source.
• Gene AI: Switch, on by default. "When on, Gene sends the first message to new leads. Does not affect replies, which follow each channel's Gene AI switch on Flows, Inbound."
• Your forms (website and Meta sources): each form with its own Capture leads and Gene sends the first message switches, a Send these leads to select, and for website forms Tell the AI about this page. A form left alone follows the source.
  • Send the latest newsletter to new sign-ups (website forms and Gene forms, where the workspace has the Newsletter): off by default. On, each new person who fills in that form gets the last newsletter you sent, by email, once. It goes out within a few minutes of the sign-up, on the same campaign that newsletter went out on, so it shows in that newsletter's results. Nobody gets it twice: not someone who signs up again, and not someone who already received that newsletter. It is not sent to anyone on Do not contact, anyone who unsubscribed, or a contact with no email address. If you have not sent a newsletter yet, or you paused or cancelled the last one, nothing is sent.
• Per-campaign context (Meta and Instagram only): one block per ad campaign (connected lead form).
  • Previews what the AI reads from the ad: the form's cover image(s), context-card title (headline), body, CTA text, and up to six form questions.
  • A per-form text box sets context applied only to that campaign's leads, so a Sora lead and a Zaya lead get the right pitch. Gene follows it on every reply to that campaign's leads, not only the first.
• General context for the AI: Text box. A short instruction appended to the AI prompt for every lead from the source, on every reply to them for the whole conversation (First-reply guidance in AI > Sales agent is the one used only on the first reply). The WhatsApp sources (a lead who messages one of your WhatsApp numbers first, however it is connected) share one set of instructions.
  • Meta and Instagram sources show a Generate from ads / Regenerate from ads button (busy label "Analyzing...") that fills it by vision analysis of the ad creative.
  • Left blank, it is saved as empty.
• Where to send leads (webhook URL): Token-ingest sources only, and never on a source a form made (its form has its own link and embed code). Read-only /api/webhooks/inbound/<token> with a Copy button and a developer sample-payload disclosure.
• Field mapping is its own tab (see Field mapping options).
• Who gets the lead (Lead routing): see Lead routing options.
• When a lead arrives: Start in pipeline stage (Select: "No stage" plus each stage of your pipelines, grouped by pipeline when you have more than one). It is set to Contacting when your pipeline has one.
  • A source never adds tags to its leads. The source is recorded on the contact itself, and tags are only ever added by a person (see Tags).
  • There is no lead temperature setting here.
• Footer: Delete source and the autosave marker (see Saving and deleting a source).

Sources made by a form#

On a source made by a form in Flows > Forms, This source belongs to the form ... replaces both Not published yet and Where to send leads.

• It has an Open the form link. Inside the form builder it points at the form's own controls instead: Publish at the top, Pause form in the ... menu and the Share tab.
• The form publishes, pauses and shares its source, so the source has no Publish of its own and no webhook URL.
• A status change on such a source is refused with "This source belongs to the form ... Publish or pause it from the form, under Flows, Forms."
• A source whose form was deleted says so and cannot be published again.

Lead routing options#

On Split by percentage, a total other than 100 warns "saving anyway will normalize". A total of 0 prompts you to set at least one.

Any option other than Default wins over the team rotation for this source's leads, so the Routing list and its weights are skipped for them. If the option has nobody it can pick, the lead goes to the team rotation instead.

Saving and deleting a source#

• Delete source opens a confirm dialog, "Delete this lead source?", with Keep it / Delete source.
  • The source stops receiving leads and is removed. Leads already in the inbox are kept.
  • On a form's source, the dialog adds that the form is deleted with it and its link stops working.
• There is no Save or Cancel button. Settings tab changes save on their own, and the X or a click outside closes the editor.

Source editor, Leads tab#

Every lead the source has brought in, newest first, up to the 50 most recent ("The 50 most recent leads from this source." when there are more).

• Each row shows the lead's name (or email or phone when there is no name), email and phone, and the day it came in.
• Each row opens that lead's conversation in the Inbox. A lead nobody has messaged yet opens on their contact page.
• Empty state: "No leads from this source yet." Leads show up here as soon as one comes in.

Field mapping options#

The Field mapping tab shows for custom and webhook-style sources, or any source with a webhook token. It maps incoming payload keys (nested keys flatten to "Parent > Child") to Gene's contact fields, with an optional clean-up per row, grouped as:

• Mapped to Gene App
• Saved as extra info
• Tracked automatically
• Not imported

The options:

• Field options: First name, Last name, Full name (auto-split), Email, Phone, Neighborhood, City, Budget (min), Budget (max), Bedrooms, Bathrooms, Property type, Notes, plus Skip ("Don't import") and Miscellaneous (misc:<key>).
• Clean-up options: No clean-up, Trim spaces, Lowercase, Uppercase, Phone format (+countrycode), Digits only.
• AI-suggested rows carry a sparkle marker until confirmed.

Ad click ids (fbclid, gclid, wbraid, gbraid, ttclid, msclkid and similar) sit under Tracked automatically. They are always kept as the lead's ad attribution, whatever the mapping says, and used to report results back to your ad platform.