Help

Sign in with your email and password, or with a magic link. Your account comes with an agency and a first client workspace, and a 14-day trial with Growth limits.

The setup checklist walks you through the essentials: connect Facebook, add a dataset for the Conversions API, choose the quality milestone, then invite your team. Lead capture starts as soon as one Page is connected.

Each client is a separate workspace with its own leads, Meta connection, Google Sheet, automations, team and reports. Switch between them from the menu at the top left.

• Agency owner / admin: every workspace, billing, the agency report, and creating or deleting workspaces.
• Client admin: everything inside one workspace, including settings and the team.
• Sales manager: all leads, the dashboard and reports, assigning leads.
• Sales rep: their own and unassigned leads, the pipeline and inbox.

Ownership of the agency changes only through Team → Transfer ownership.

Settings → Connect with Facebook signs you in with Meta and asks for the permissions the CRM needs: leads_retrieval, pages_manage_metadata, pages_show_list, pages_read_engagement, ads_read and business_management. If you skip one, the wizard says which feature won’t work.

Choose the Pages whose Instant Forms belong to this client (a Page can belong to one workspace only), the ad account for spend and cost per lead, and the dataset (pixel) that receives Conversions API events.

Settings → Lead forms lists every form on each Page and can send a Meta test lead through the whole flow.

Leads move through stages by drag and drop (or keyboard: Space to pick up, arrows to move). Every move is timestamped in the lead’s history.

The quality milestone is the stage that proves a lead was worth it — Site Visit Done for real estate, Demo Class Attended for education, Consultation Done for clinics. The Settings page suggests one from your own data. It and every later stage count as quality leads in reports.

Stages marked “send to Meta” create a Conversions API event the first time a lead reaches them. As Meta asks, every stage is reported in order: if a lead jumps from New to Won, the stages in between are sent first. Each event is sent once per Meta lead ID, so a person who fills in a second Lead Ad gives feedback to both ads.

Events are queued, sent in the background and retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours. Errors retrying can’t fix (an expired token, a missing permission or dataset) fail straight away with one alert, so you can fix the cause and use Retry now on Meta events. Meta only accepts CRM events up to 7 days old.

Meta events shows each event’s payload and Meta’s response, and delivery by event name, so you can match what you see in Events Manager. Use a test event code in Settings to check delivery without affecting real data.

With WhatsApp Cloud API connected, every new lead with a valid phone number gets your approved template within seconds. Replies appear in the Inbox and on the lead.

Free-form messages are allowed only within 24 hours of the lead’s last message; outside that window, send a template.

Settings → Google Sheets: share the sheet with the address shown, paste its link, and choose one-way (CRM → Sheet) or two-way sync. Leads and changes are written within seconds; edits in the sheet come back every 5 minutes.

In the sheet you can change Status (a stage name), Name, Phone, Email and Notes, and add new rows. Rows are matched by CRM ID, so sorting is safe. New rows are checked for duplicates by phone and email. If the same field changed in both places, the CRM’s value wins and the conflict is listed on the Sheets page.

An automation is a trigger (new lead, lead reaches a stage, lead is scored), optional conditions (source, score, stage, campaign, ad set, has phone or email, assigned) and steps that run in order.

• Send Meta event — a custom Conversions API event, once per lead.
• Update Google Sheet, Notify (managers, the assigned rep or your alert channels), Assign (to someone or round robin), Move to stage, Send WhatsApp template.
• Wait (up to 7 days) and Continue only if — re-check conditions, e.g. still in New after 2 hours.

Each automation shows its recent runs step by step. Automations that trigger other automations stop after three hops.

The dashboard and Reports show leads, the funnel, qualification rate, cost per lead (CPL), cost per quality lead (CPQL) and failed events by campaign. The Agency page compares every client.

Reports → Pilot compares volume, qualified rate and downstream results before and after you start sending the quality milestone, so you can show a client what changed.

Billing shows your plan, trial and usage across all workspaces. Plans are paid monthly in INR through Razorpay; choosing one opens Razorpay’s secure checkout.

Limits cover client workspaces, team seats (invitations count), automations and Google Sheets. Leads are never dropped: over the monthly lead allowance, every lead is still captured and sent to Meta, but AI scoring switches to rules until the next month or an upgrade.

Cancelling keeps your plan until the end of the paid period; your data is kept on the free plan.

Every workspace’s data is isolated in the database itself, not just in the app. Access tokens are stored encrypted and never shown again; webhooks from Meta and Razorpay are verified by signature.

Settings → Privacy and data: export all leads as CSV, set a retention period (untouched leads are deleted nightly) and, for agency admins, delete a workspace.

People can request deletion of their data at /delete-data. Email requests are confirmed from the inbox before the business sees them.

The Audit log records who changed settings, connections, team access, automations and billing. It never stores lead contact details.

• No leads arriving: check the Page shows “receiving leads” in Settings, then send a test lead from Lead forms. Leads Meta couldn’t deliver are picked up by the hourly backfill (up to 7 days back on the first run).
• Events failing with a token error: reconnect Facebook; Meta tokens expire and you get a warning 7 days before.
• Sheet sync stopped: the sheet was unshared or deleted; the Sheets page shows the error.
• Something else: the Admin page has a launch checklist of every integration.