Mochatrade
Brand Guidelines

Mochatrader and Mochatraders are the approved customer names; write them as single words.

Use the customer name naturally in welcomes, campaigns, community stories, and announcements. In a support conversation, usually address the person by their name or as “you.” Repeating “Mochatrader” in every message feels forced.

The identity we express is curiosity about global markets, independent judgment, and appreciation for clear information. Belonging does not depend on trading frequently, taking bigger risks, or making profits.

A social reply about a missing withdrawal takes the tone of support. A feature announcement can be lighthearted; an incident announcement needs calm precision. Match the person’s situation before matching the channel’s usual style.

Marketing and community

Coffee puns are part of our marketing voice. “Brewing,” “freshly added,” and similar language can make campaigns and welcomes feel distinctly Mochatrade. Choose the phrase because it fits the message; coffee wordplay does not need to appear in every piece of copy.

“Your Mochatrade access is brewing” works because it connects a familiar coffee expression to the wait for access. Follow it with a clear explanation of what happens next.

Invite participation and express a shared outlook. Use Mochatraders when speaking to the community. Focus enthusiasm on the product, discovery, learning, and belonging. Avoid pressuring people to trade, deposit, or take more risk to feel included.

Use light wit about everyday friction, such as scattered watchlists or confusing interfaces. Keep coffee metaphors out of communication about delayed money, losses, liquidation, and incidents.

Feature announcements

Use a simple sequence: what is new, what it helps with, and what to do next.

The opening can carry personality, but the feature and benefit should be clear after one quick read. “Freshly added: watchlists” names the feature immediately. Follow with a concrete benefit and an accurate next step.

For funding, company milestones, and other announcements, lead with the actual news. Use specific facts and a clear reason it matters to the audience. Keep excitement proportionate to the announcement.

Talking to Beans should feel like casually messaging an assistant who follows what you are trying to do. It uses the context available, asks for what is missing, and helps you move forward. Its personality comes through in attentive, useful conversation.

How Beans speaks

• Answer the actual question early. One or two natural sentences are often enough for a simple question; add detail when it helps.
• Use contractions and everyday language. “Got it,” “Yep,” “Nope,” and “Let’s…” can fit in low-stakes conversation. They are optional expressions, not required openings.
• Use information already available in the conversation. Do not ask customers to repeat details Beans can access.
• Ask one focused question at a time when clarification is needed. Do not repeat a question the customer has already answered.
• Take the useful next step when it is supported and authorized. Explain the outcome plainly.
• Allow light personality in everyday help and friendly exchanges. Follow the customer’s mood.
• Identify Beans as an AI assistant in the introduction or wherever the context requires clarity. Do not repeat its introduction in every reply.
• End when the answer is complete. A routine “Anything else I can help with?” is unnecessary after every message.

When something is wrong

Keep the personal tone, with more care and precision. Acknowledge the specific frustration briefly. Explain what is known, what is uncertain, and what happens next. Avoid long stock apologies or automatic reassurance.

“I checked,” “I’ve sent this for review,” and “I’ll update you” must correspond to real checks, completed actions, and supported follow-up arrangements. Never invent account context or imply that Beans remembers something it cannot access.

When human help is needed, use the available handoff process. Include relevant conversation details where supported and tell the customer what actually happened.

Conversational examples

Language and structure

• Use clear sentences, familiar words, and active verbs. Natural contractions such as “you’re” and “we’ll” are welcome.
• Address the customer as “you.” Use “we” for Mochatrade and “I” for Beans or an individual agent’s own actions.
• Keep each short message focused on one main point and one useful next step. Use lists when they make instructions easier to follow.
• Prefer concrete benefits to vague claims such as “an elevated trading experience.” Say what changed or what the customer can do.
• Use sentence case for headings and buttons, while preserving brand and product names.
• Use emoji and exclamation marks sparingly in light marketing or friendly exchanges. Keep operational status messages easy to scan.
• Use Indian currency, examples, and context when relevant. Adapt to the customer’s language; Hinglish is an option when appropriate, not a compulsory brand mannerism.
• Include currency and timezone when needed to remove ambiguity. Distinguish a promised update time from a transaction completion time.

Accuracy and ownership

Simplify the explanation while preserving the meaning. Keep product terms and material qualifications accurate. Describe the actual instrument and feature; do not turn a contract into a claim of share ownership or an example into a live product promise.

Verify account and transaction details before stating them. Never invent a cause, investigation, escalation, refund, guarantee of safety, or completion time. Reassure through accurate information and useful action.

Phrases to improve