- Brand
- 33CRM
- Category
- Sales & CRM
- Primary Subcategory
- B2B Sales CRM Platforms
Integration details
Description
33CRM is a business CRM connection for company administrators to review leads, customers, deals, pipeline, bookings, conversation operational metadata, stored Meta advertising data, WhatsApp campaign aggregates, and bounded business performance reports in ChatGPT. The connection is scoped to the company bound to the administrator’s OAuth grant and is read-only. It cannot create, update, delete, assign, book, cancel, send, launch, sync, refresh, or select another tenant. Conversation message bodies, attachments, clinical notes, appointment notes, credentials, recipient lists, WhatsApp template content or variables, advertising audiences, and creative URLs are not returned. Some tools may return CRM contact fields such as name, phone number, and email when those fields are part of the requested business record.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- B2B Sales CRM Platforms
- Secondary Subcategories
- None listed
- Brand
- 33CRM
- Access
- Account required
- First tracked
- 2026-10-20
- Tool count
- 24
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Your score is coming
ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.
What discovery looks like

Get alerts for 33CRM
Get updates when 33CRM’s Discoverability Score or category rank changes.
Competing in ChatGPT B2B Sales CRM Platforms
View Category24 tools agents can invoke
Read stored daily Meta ad insights of the authenticated company by optional account_id, campaign_id or ad_id. Use it to compare daily delivery and spend. Does not call or refresh Meta. Inclusive provider reporting calendar dates, default most recent 30 dates anchored to the current UTC date, maximum 366 days. One bound anchors 30 days. Each row includes account currency, reporting timezone and sync freshness. Spend is a four-decimal currency string. Unknown currency yields null amount. Daily reach must not be summed as unique reach. Provider leads are not CRM conversions. Rows are paginated, not complete period totals; no aggregate rates are returned. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Get one booking of the authenticated company using its UUID. Use it after list_bookings to inspect schedule, status and tenant-checked relationships. No notes, clinical type labels, reminders or event metadata. Not date-filtered. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Aggregate the authenticated company's appointments for a period: how many were scheduled, how many are marked attended, and the split by stored status and by branch. Use it to review booking volume and attendance for a window without listing individual appointments. Metric basis: appointments whose scheduled_at falls in the window, counted by the status and branch on the row now. attended_count is exactly the ATTENDED rows. attended_share_of_all_bookings divides that by ALL appointments in the window whatever their status — including cancelled, no-show and still-upcoming ones — so it is not a show-up rate over completed appointments, and it is null rather than 0 when the window holds no appointment. A branch that is unset or belongs to another company is merged into one unattributed bucket with a null reference. Nothing about treatment, service, health, outcome or revenue is read or inferred: no appointment type, note or clinical field is selected, and this tool reports no money. Date basis: appointments.scheduled_at, which unlike list_bookings looks BACKWARD by default. Dates: date_from and date_to are inclusive UTC calendar days (YYYY-MM-DD). With neither supplied the most recent 30 days are returned. With only date_from supplied the window is that day plus the following 29 days; with only date_to supplied it is that day and the preceding 29 days. Either way the window is 30 days anchored on the bound you gave, so supply both bounds when you want a different span. The range may not exceed 366 days and may not be reversed. limit and offset page the by_status and by_branch breakdowns, each of which reports its own paging block with the breakdown total, has_more and next_offset; the totals block always covers the whole period. by_status lists only the statuses that occurred, and it is paged, so a status missing from the page in hand is not evidence that it matched no appointment. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Get one conversation of the authenticated company: its operational metadata and message counters. Use it to judge how busy or stale a conversation is without reading what was said. Returns the conversation state plus total, inbound, outbound and per-sender message counts and first/last message timestamps. It returns no message content, no attachments and no media URLs, so it cannot be used to read a customer conversation. A conversation outside this company is reported exactly like one that does not exist. Not date-filtered and not paged. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Count the authenticated company's conversations created in a period, split by channel and by status. Use it for conversation volume and the current state of that cohort. Metric basis: conversations whose created_at falls in the window, counted by the channel and status they carry NOW, reported as as_of. status is a live snapshot rather than the status held during the window, so a conversation created in the window and resolved later counts as resolved and the same window can answer differently later. No response time, first-reply time, handling time, SLA or escalation-outcome figure is reported; this tool does not derive those metrics from validated event timestamps. It returns no message text, attachments, metadata, provider addresses or recipient identities. Date basis: conversations.created_at. Dates: date_from and date_to are inclusive UTC calendar days (YYYY-MM-DD). With neither supplied the most recent 30 days are returned. With only date_from supplied the window is that day plus the following 29 days; with only date_to supplied it is that day and the preceding 29 days. Either way the window is 30 days anchored on the bound you gave, so supply both bounds when you want a different span. The range may not exceed 366 days and may not be reversed. limit and offset page the by_channel and by_status breakdowns, each of which reports its own paging block with the breakdown total, has_more and next_offset; the total always covers the whole period. Both breakdowns list only the values that occurred, and they are paged, so a channel or status missing from the page in hand is not evidence that it matched no conversation. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Get one customer of the authenticated company. Use it after list_customers to read contact and acquisition details. Personal data includes name, phone and email. No clinical notes, addresses, metadata or social identifiers. Not date-filtered. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Get one deal of the authenticated company by its string transaction code. Use it after list_deals to inspect value, payments and tenant-checked relationships. No clinical title, lost reason or payment-method narrative. Not date-filtered. Money: amounts are two-decimal strings and currency is this company's single configured code. currency is null when this company has no usable currency code configured. An unknown currency is reported as null and is never presented as USD or any other guess, so a null-currency amount must not be compared with, converted from or added to an amount in a known currency. An amount is null when the stored value is absent or not a finite number; null means unknown, never zero. The underlying columns are 32/64-bit floats rather than exact decimals, so these strings are a rounded rendering of the stored value and sums inherit that float error; they are not exact accounting decimals. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Get one lead of the authenticated company together with its pipeline stage history. Use it after list_leads to inspect a single lead's business record and how it moved through the pipeline. Returns the same allowlisted business fields as list_leads, the linked customer reference, and stage transitions with company-checked from/to stages and the user who made each change. It never returns lead notes, the free-text comment, lost/won reasons or any clinical narrative; a lead outside this company is reported exactly like a lead that does not exist. limit and offset page the stage history only. Not date-filtered. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Aggregate the authenticated company's STORED Meta advertising rows for a period into one row per advertising account: impressions, clicks, provider-reported leads and spend. Use it for account-level delivery totals; use get_ad_insights for the underlying daily rows. It does not call or refresh Meta, so the figures are only as fresh as each account's last_synced_at. Metric basis: ads_insights.date is a provider DATEONLY reporting date in the account's own reporting timezone, so two accounts in different timezones do not cover the same instants. Spend is summed exactly in four-decimal account currency; a value that does not fit that scale is excluded and counted in rows_missing_spend rather than rounded in. Unknown account currency yields a null amount. Totals are never combined across accounts or currencies, and daily_rows 0 means no stored data, not zero delivery. Deliberately absent: unique reach, which is not additive and is therefore not summed or returned, every derived rate such as CTR, CPC or ROI, budgets, audiences, creatives, credentials and any attribution between advertising and CRM records. provider_leads are Meta-reported results, not CRM leads, deals or revenue. Every summed row is proved to belong to this company, through its ad, campaign and account, by the same query that reads it, so a row whose ownership or provider changed is dropped rather than counted under a stale owner. Filters: account_id, which must be an advertising account of this company. Date basis: ads_insights.date, inclusive provider reporting calendar dates. Defaults to the most recent 30 dates anchored to the current UTC date, maximum 366 dates. One bound anchors a 30-day window, starting at date_from or ending at date_to. Provider reporting days are not converted into UTC event intervals. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Get one stored Meta campaign of the authenticated company by its internal UUID from list_meta_campaigns. Use it to inspect campaign status and schedule. Current snapshot; not date-filtered. Returns safe campaign and account metadata, not live insights, budgets, credentials or audiences. Does not refresh Meta. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Aggregate the authenticated company's deals for a period: deal count, booked value and amount paid to date, broken down by pipeline stage and by owner. Use it for period deal performance instead of paging list_deals, and use sales_summary when you want lead-cohort counts, which mean something different and are unchanged by this tool. Metric basis: deals whose deal_date falls in the window, grouped by the stage and owner they carry now. booked_value sums the agreed deal value. amount_paid_to_date sums each deal's CURRENT collected total; it is NOT cash received during the window and NOT recognized revenue; this report does not read a dated payment ledger. A stage or owner that is unset, deleted, or belonging to another company, is merged into one unattributed bucket with a null reference; no foreign id or name is ever returned. A group with no deals reports a real "0.00"; a null amount means the sum could not be read and never means zero, and a merged bucket reports null whenever any group inside it was unreadable, so a partial total is never shown as a complete one. booked_value_rows and amount_paid_rows count deals carrying a stored, non-NULL amount: that is coverage, not proof each value was readable. Money: amounts are two-decimal strings and currency is this company's single configured code. currency is null when this company has no usable currency code configured. An unknown currency is reported as null and is never presented as USD or any other guess, so a null-currency amount must not be compared with, converted from or added to an amount in a known currency. An amount is null when the stored value is absent or not a finite number; null means unknown, never zero. The underlying columns are 32/64-bit floats rather than exact decimals, so these strings are a rounded rendering of the stored value and sums inherit that float error; they are not exact accounting decimals. Date basis: deals.deal_date. Dates: date_from and date_to are inclusive UTC calendar days (YYYY-MM-DD). With neither supplied the most recent 30 days are returned. With only date_from supplied the window is that day plus the following 29 days; with only date_to supplied it is that day and the preceding 29 days. Either way the window is 30 days anchored on the bound you gave, so supply both bounds when you want a different span. The range may not exceed 366 days and may not be reversed. limit and offset page the by_stage and by_owner breakdowns, each of which reports its own paging block with the breakdown total, has_more and next_offset; the totals block always covers the whole period. A stage or owner missing from the page in hand is not evidence that it has no deals. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Read stored aggregate counters for one WhatsApp campaign of the authenticated company by its internal UUID. Use it after list_whatsapp_campaigns to review sent, failed and skipped counts. Current snapshot; not date-filtered. Sent is not delivered or read. Counters may lag and need not reconcile; no conversion or success-rate inference is provided. No recipients, template content/variables or audiences. This tool cannot launch, cancel or send messages. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
List stored Meta ads of the authenticated company, optionally by account_id, campaign_id and exact provider status. Current snapshot; not date-filtered. Use it to find the internal ad UUID for get_ad_insights. Returns safe names/status and company-checked campaign/account metadata; no creative URLs or credentials. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
List bookings of the authenticated company. Use it to review appointments by status, branch_id, sales_rep_id or lead_id. Date basis: appointments.scheduled_at, inclusive UTC calendar days. Defaults to today and the following 29 days. Supply both date_from and date_to for a historical or custom period of at most 366 days. One bound anchors a 30-day window, starting at date_from or ending at date_to. Returns scheduling metadata and tenant-checked contacts, branch and owner; never appointment notes, treatment labels or event metadata. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
List branches belonging to the authenticated company. Use it to find a branch ID for booking filters. Returns ID and name only. Current snapshot; not date-filtered. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
List the authenticated company's customer conversations with their operational state. Use it to see which conversations are open, escalated or waiting, on which channel, and who owns them. Filters: channel and status. Returns operational metadata only — channel, status, priority, AI enablement, sentiment, company-checked contact, lead and assignee references, and activity timestamps. It never returns message text, attachments, media URLs, conversation metadata, provider addresses or channel configuration. Date basis: conversations.updated_at (last activity). Dates: date_from and date_to are inclusive UTC calendar days (YYYY-MM-DD). With neither supplied the most recent 30 days are returned. With only date_from supplied the window is that day plus the following 29 days; with only date_to supplied it is that day and the preceding 29 days. Either way the window is 30 days anchored on the bound you gave, so supply both bounds when you want a different span. The range may not exceed 366 days and may not be reversed. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
List the authenticated company's customer records. Use it to look up customers created in a period and their contact details. Returns identifiers, name, phone, email, acquisition source, WhatsApp opt-out state and record timestamps. Name, phone and email are personal data and are shared with the connected app. Addresses, tags, arbitrary metadata and social handles are not returned. Date basis: clients.created_at, the moment the customer record was created in the CRM. Dates: date_from and date_to are inclusive UTC calendar days (YYYY-MM-DD). With neither supplied the most recent 30 days are returned. With only date_from supplied the window is that day plus the following 29 days; with only date_to supplied it is that day and the preceding 29 days. Either way the window is 30 days anchored on the bound you gave, so supply both bounds when you want a different span. The range may not exceed 366 days and may not be reversed. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
List the authenticated company's deals with their stage, owner, customer and money. Use it to review deal flow for a period or for one stage or owner. Filters: stage_id and owner_id, both of which must belong to this company. Money: booked_value is the agreed deal value and amount_paid is what has been collected; they are never combined and never summed across currencies. Money: amounts are two-decimal strings and currency is this company's single configured code. currency is null when this company has no usable currency code configured. An unknown currency is reported as null and is never presented as USD or any other guess, so a null-currency amount must not be compared with, converted from or added to an amount in a known currency. An amount is null when the stored value is absent or not a finite number; null means unknown, never zero. The underlying columns are 32/64-bit floats rather than exact decimals, so these strings are a rounded rendering of the stored value and sums inherit that float error; they are not exact accounting decimals. Deal titles, lost reasons and payment methods are not returned. Date basis: deals.deal_date. Dates: date_from and date_to are inclusive UTC calendar days (YYYY-MM-DD). With neither supplied the most recent 30 days are returned. With only date_from supplied the window is that day plus the following 29 days; with only date_to supplied it is that day and the preceding 29 days. Either way the window is 30 days anchored on the bound you gave, so supply both bounds when you want a different span. The range may not exceed 366 days and may not be reversed. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
List the authenticated company's leads, newest activity first. Use it to find leads by workflow status or pipeline stage and to see who owns them. Filters: status (lead workflow token), stage_id (must be a stage of this company). Returns per lead: identifiers, contact name, phone and email, status, source, company-checked stage and owner, and lifecycle timestamps. Free-text lead comments, lost/won reasons, ad referral payloads and date of birth are never returned. Date basis: leads.updated_at (last change to the lead). Dates: date_from and date_to are inclusive UTC calendar days (YYYY-MM-DD). With neither supplied the most recent 30 days are returned. With only date_from supplied the window is that day plus the following 29 days; with only date_to supplied it is that day and the preceding 29 days. Either way the window is 30 days anchored on the bound you gave, so supply both bounds when you want a different span. The range may not exceed 366 days and may not be reversed. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
List stored Meta advertising campaigns of the authenticated company. Use it to find campaigns by account_id or exact provider status in this snapshot; not date-filtered. Returns names, objectives, status, schedule and account currency/timezone/sync freshness. No budgets, credentials or audiences. Does not refresh Meta. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
List active, non-deleted sales representatives of the authenticated company. Use it to find an owner ID for booking filters. Returns ID and display name only. Current snapshot; not date-filtered. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
List WhatsApp campaigns of the authenticated company. Use it to review campaign status and stored aggregate counters by optional status. Date basis: whatsapp_campaigns.created_at, inclusive UTC calendar days. Defaults to the most recent 30 days, maximum 366. One bound anchors a 30-day window. No recipients, template bodies/variables, audiences or message content. Sent is not delivered or read; counters may lag. This tool cannot launch or cancel campaigns. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Summarize the authenticated company's current pipeline: deal count and total booked value per stage. Use it for a snapshot of where deals sit right now. This is a present-state snapshot, not a period report and not a revenue report: it is not date-filtered, and booked_value sums agreed deal value rather than collected payments. Money: amounts are two-decimal strings and currency is this company's single configured code. currency is null when this company has no usable currency code configured. An unknown currency is reported as null and is never presented as USD or any other guess, so a null-currency amount must not be compared with, converted from or added to an amount in a known currency. An amount is null when the stored value is absent or not a finite number; null means unknown, never zero. The underlying columns are 32/64-bit floats rather than exact decimals, so these strings are a rounded rendering of the stored value and sums inherit that float error; they are not exact accounting decimals. A stage with no deals reports deal_count 0 and booked_value "0.00", which is a real zero; a null amount instead means the total could not be read. Stages are ordered as they were created; limit and offset page over the stages. Paging: limit defaults to 50 and is capped at 100; out-of-range or fractional values are rejected rather than clamped. offset may not exceed 10000: when more rows match than paging can reach, pagination.has_more stays true, pagination.next_offset is null and pagination.pagination_limited is true — narrow the filters or the date range rather than treating the page as the complete result. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
Return the authenticated company's lead-cohort sales figures, matching the CRM sales dashboard. Use it for period performance: how many leads arrived, how many were qualified, attended a visit, were won and were lost, plus the breakdown by pipeline stage and by lead source. Metric basis: every figure counts LEADS in the date cohort, not deals and not revenue. won_leads counts leads that entered a stage flagged as won. Rates are fractions of total_leads and are null when the cohort is empty. This tool reports no money. Date basis: the lead's business date, falling back to its creation timestamp. Dates: date_from and date_to are inclusive UTC calendar days (YYYY-MM-DD). With neither supplied the most recent 30 days are returned. With only date_from supplied the window is that day plus the following 29 days; with only date_to supplied it is that day and the preceding 29 days. Either way the window is 30 days anchored on the bound you gave, so supply both bounds when you want a different span. The range may not exceed 366 days and may not be reversed. limit and offset page the by_stage and by_source breakdowns. Read-only: this tool only reads data for the company that authorized this connection. It cannot create, change, delete, assign or send anything, and it never accepts a company, tenant or workspace argument.
33CRM ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve 33CRM's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are 33CRM alternatives on ChatGPT?
As of 2026-10-20, 33CRM competes with HubSpot, Attio, Close, Zoho CRM, Agiled, Alaz, Asbie, Badger Maps (Advanced) and 47 more in ChatGPT B2B Sales CRM Platforms, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.