| name | sales-engagebay |
| description | EngageBay platform help — affordable all-in-one CRM + marketing + sales + service suite for startups and SMBs (Marketing Bay, Sales & CRM Bay, Service Bay): email automation, landing pages, deals/pipelines, helpdesk tickets, and a REST API (raw API-key Authorization header, base app.engagebay.com, JSON only via Accept header, cursor pagination, outbound-only webhooks). Use when an EngageBay API call returns XML instead of JSON, you can't push data INTO EngageBay because it has no incoming webhooks, a deal created via the API doesn't show in the pipeline (track/milestone name case mismatch), you hit a 429 from the plan-gated monthly API quota, per-user/per-contact pricing keeps climbing, automation-node or contact limits are too low on your tier, or you're weighing EngageBay as a cheaper HubSpot/Keap/Ontraport alternative. Do NOT use for comparing CRMs across vendors (use /sales-crm-selection) or email-marketing strategy across tools (use /sales-email-marketing). |
| argument-hint | [describe what you need help with in EngageBay] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","crm","platform"] |
| github | https://github.com/engagebay |
EngageBay Platform Help
EngageBay is an affordable all-in-one CRM + marketing + sales + service suite for startups and SMBs — Marketing Bay (email, automations, landing pages, forms), Sales & CRM Bay (contacts, deals, pipelines, tasks), and Service Bay (helpdesk tickets, live chat), on one shared contact database with a REST API and outbound webhooks.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Figure out which of these the user needs (ask only if their prompt doesn't already say):
-
What kind of problem is this?
- A) API / webhook / integration build (auth, JSON vs XML, pagination, syncing data)
- B) Automation, sequences, or landing pages not behaving
- C) Pricing, plan, contact/automation-node limits, or which Bay to buy
- D) Deliverability / email sending limits
- E) Choosing whether EngageBay is the right tool at all
-
Which module(s)? Marketing Bay, Sales & CRM Bay, Service Bay, or the All-in-One Suite — features and limits differ by module and tier.
Skip-ahead rule: if the user's prompt already has enough context, skip to Step 2 or Step 3.
Step 2 — Route or answer directly
| Problem domain | Route to |
|---|
| Comparing EngageBay vs HubSpot/Keap/Ontraport/Zoho or picking a CRM | /sales-crm-selection {user's question} |
| Email-marketing strategy (segmentation, deliverability) across platforms | /sales-email-marketing {user's question} |
| General inbox-placement / sender-reputation strategy | /sales-deliverability {user's question} |
| Multi-step funnel / landing-page strategy across tools | /sales-funnel {user's question} |
| Connecting EngageBay to other tools (Zapier/Make/native) | /sales-integration {user's question} |
| Contact enrichment for CRM records | /sales-enrich {user's question} |
When routing, give the exact command, e.g. "This is a CRM-comparison question — run: /sales-crm-selection should I move from EngageBay to HubSpot".
Step 3 — EngageBay platform reference
Read for the full reference — capabilities & automation surface, pricing/plan gates, data model (JSON shapes), integration recipes (cURL + Python), and integration patterns. For raw API detail (endpoints, auth, webhooks, every resource), read .
