Lead management
Every lead with email, phone, Instagram and LinkedIn. Stages, scores, CSV import, search — and which email each lead responded to.
Wish CRM keeps your leads, email campaigns, replies, LinkedIn posts and Instagram conversations in one place. Give an agent a single scoped connection and it can work all of it for you.
Every lead with email, phone, Instagram and LinkedIn. Stages, scores, CSV import, search — and which email each lead responded to.
Write once with merge tags, pick an audience by stage, press Start. Emails leave one at a time inside your daily limit.
No reply after N days? A follow-up goes out in the same thread — only to the people who stayed silent.
Replies are read from your mailbox every two minutes and land in the right conversation: Sent → Reply → Follow-up → Replied back.
Sent, delivered, opened, replied, follow-up replies and bounces — computed from what actually happened, never sample data.
Your agent drafts posts, you approve, the CRM publishes. Nothing goes public without a human pressing the button.
DMs and comments from every channel in one inbox. Reply from the CRM, turn a person into a lead, and watch conversion and returning contacts.
Drop a contact form on any of your sites. Submissions become leads instantly — spam-trapped, rate limited and locked to your domain.
Lead scores move with real behaviour: opens, clicks, replies, enquiries. A Telegram ping tells you the moment someone answers.
SPF, DKIM and DMARC aligned sending, one-click unsubscribe headers, bounce handling, and unsubscribed leads are never emailed again.
Enter the mailbox once. The password is encrypted on your own server and the connection is tested on the spot.
Add them by hand, import a CSV, or let an agent create them through MCP.
Subject, body, optional follow-up. It stays a draft until you press Start.
Conversations, lead stages and dashboard numbers update on their own.
Paste one URL into Claude or any MCP client, tick what it may do, done.
Claude does not have your mailbox or your Instagram — and it should not. The CRM holds those connections; an agent gets a single, scoped doorway into it. Paste the URL, approve on a Wish CRM page, choose exactly what it may do.
https://crm-api.wishmaster.space/mcplist_leadscreate_leadupdate_leadsend_emailcreate_campaignset_campaign_statuslist_threadsadd_thread_messageget_dashboardlinkedin_create_draftsocial_inboxsocial_replylist_lead_formsEvery page and every API call sits behind sign-in; sessions live in an HttpOnly, Secure cookie.
Agents connect with OAuth 2.1 + PKCE or scoped API keys. Keys are stored as hashes and shown once.
Per-agent permissions: read-only by default, sending and publishing are separate switches.
A full history of which agent called what, from which IP, and what was blocked.
Mailbox and social tokens are AES-256 encrypted at rest. The backend runs isolated, non-root, on your own server.
Login and key attempts are rate limited; all input is validated and queries are parameterised.
Anything that speaks MCP or plain REST: Claude, ChatGPT-based agents, Kira, Hermes, OpenClaw, or your own scripts.
Only if you give its key the email permission — and every call is written to the connection history. Revoke a key and it stops instantly.
In a Postgres database on your own cloud server. The browser never talks to that server directly.
No. WhatsApp is intentionally out of scope; the hub covers email, LinkedIn, Instagram, Messenger, Telegram and your website forms.
Private workspace. Access is by invitation.