Eva on X: receive enquiries and reply in one place

What is it?

The owner connects the office account through the platform consent flow. Once the inbox is activated, stored conversations and supported office-post replies appear with the channel identity and Riyadh timestamps. The owner can answer personally or take a conversation over to stop Eva on that thread. Members can view the page only when the owner permits social access. That permission does not allow connecting accounts or sending replies. Finance and call-center identities cannot access social pages. Connection does not mean every message format is supported, so the activation controls explain platform limits.

Who is it for?

• An office receiving enquiries about its X posts that needs a clear record of each request.
• An owner who answers personally and returns a conversation to Eva when ready.
• A team that needs visibility without granting staff social-account administration.
• An office qualifying customers privately without exposing their contact details below a public post.

What problem does it solve?

• Requests scattered between a native social app and the CRM are harder to follow.
• An assistant and employee can answer together unless takeover is explicit.
• A public reply exposing customer details compromises privacy; Eva uses limited public copy.
• A connected account does not prove delivery or reading, and does not remove API costs.

How it works, step by step

1. Open Channels as the owner and read the X API cost notice before connecting.
2. Add a payment method in Zernio if required to enable X access.
3. Connect the office account through consent. One account is allowed; reconnecting it does not add a second.
4. Activate the X inbox separately when you accept the platform requests it can bill.
5. Open X to review DMs or the post-activity tab.
6. Enable the separate DM and public-comment AI switches only if you want automation; both default off.
7. To answer personally, select a conversation and write your message. Takeover stops Eva until you return it.
8. Keep customer information out of public replies and check send status whenever the result is unconfirmed.

What is included

• A shared inbox layout for desktop and phone.
• Owner, manager or marketing replies with durable operation identities to avoid duplicate retries.
• Periodic office-post reply refresh and storage of received comments.
• Unread counts inside EvaCore, separate from customer read receipts.
• Independent Eva settings for DMs and public replies.
• Comment counts and leads linked to commenter identities from actual office records.
• Publishing and scheduling from the Social section — coming soon: a post, thread or poll with X character counting, published now or at a Riyadh time after the owner, a manager or marketing approves it.
• A private media library and a month and week calendar; dragging a scheduled post to another day and retrying a failed one with the reason in plain words are coming soon with publishing.
• A page per post with its X link, its numbers exactly as the platform returned them, its replies and the leads it produced, plus an account overview with followers from one daily snapshot since the first capture.

Price and what others bill you

What others bill you

• Zernio passes through X API costs, including periodic refresh requests. Review billing in your Zernio account.

Annual billing is ten months' money for twelve months of service. Pricing

Related products