1. Product name
Vertex CRM — web CRM at vertexcrm.in.
2. Who uses it
Target customers are digital agencies, professional services firms, and B2B sales teams (including India-focused teams) that need a practical CRM with optional Meta advertising and WhatsApp messaging workflows—not a generic social consumer app.
3. Main features
- Accounts, contacts, leads, opportunities (pipeline)
- Activities, tasks, cases, reports, campaigns
- Multichannel Inbox: WhatsApp (AiSensy Project API + webhooks and/or Meta Cloud API), email marketing, and mailbox sync where enabled
- Inbox composer: approved WhatsApp templates, media attachments, follow-up / reminder activities, and payment-link sharing
- Role-based access control and organization administration
- Optional Meta integrations: Ads account connect/sync, Facebook Page binding for Lead Ads, WhatsApp Cloud API send/receive into Inbox
- Optional commerce integrations: live catalog / subscription cards and Razorpay payment links (via connected shop API or direct Razorpay credentials)
- Optional AI-assisted inbox/CRM suggestions that require human confirmation before writes
4. Why Meta integration is required
Customers ask to manage Meta-sourced demand inside the same CRM where they already run pipeline and follow-ups. Without Meta APIs, teams copy leads and chats manually, lose attribution, and miss response SLAs.
End-user workflow (customer admin):
- Customer signs in to their Vertex CRM organization
- Goes to Setup → Integrations (WhatsApp, Meta Ads, and related connectors)
- For WhatsApp: connects either AiSensy (Project ID + Project API key + webhook) or Meta Cloud API credentials for their business number
- For Meta Ads / Lead Ads: authorizes Vertex CRM’s Meta app against their Business assets
- CRM stores encrypted tokens scoped to that organization
- Lead Ads / WhatsApp events are ingested into that tenant’s leads and inbox
- Sales users work the record and reply in Inbox; customer can disconnect integrations at any time
5. Meta products and data (accurate scope)
| Meta surface | Data received | Actions in CRM | Why needed |
|---|---|---|---|
| Facebook Login / OAuth for Business assets | App-scoped user id, tokens, ad account & page ids | Connect/disconnect integrations | Customer-authorized access only |
| Marketing / Ads APIs | Ad account list, campaign metadata | Display/sync campaign list | Ads visibility inside CRM admin |
| Lead Ads | leadgen payloads / form fields | Create/update CRM leads | Capture paid demand without CSV export |
| WhatsApp Cloud API | Inbound/outbound message metadata & content | Inbox threads, optional lead match | Respond to customers in one workspace |
| AiSensy (BSP, non-Meta path) | Project webhook events + Project API send | Same WhatsApp Inbox lane; templates, media, status | BSP-hosted WhatsApp without direct Cloud API ops |
| Webhooks | Event notifications | Verify signatures; route to tenant | Reliable realtime ingest |
We do not claim features the product does not provide (for example a fully autonomous Instagram/Messenger production inbox, or Meta Partner status merely by publishing this page).
6. Multi-tenant ownership model
OctaVertex Media owns the SaaS application and Meta app configuration. Each customer authorizes access to their Meta assets. Customer CRM data stays in their organization tenancy. See Privacy Policy § Meta data and Data Processing Agreement.
7. Related links
Last updated: August 2026.