Email and WhatsApp · Linbo
Linbo beside your emails. WhatsApp conversations, templates and archives. From understanding requirements to preparing the next reply.
See the highlights firstHello,
Could you share the specifications and available packaging options?
We would also like to confirm the sample process before deciding on an order.
Thank you.
Summaries, labels, translations and editable drafts appear in the email. Choose favorites or highlights again to toggle them off.
Choose a Linbo action to change this email.
This page uses a fictional email and prepared demo results. Edit your draft and keep it while switching actions; reset clears it. No AI request or real email is sent.
WhatsApp · Your channel and message workspace
Explore channels, conversations, templates, history and AI assistance separately. Actual sending always follows your account and service conditions.
Pair your account with a QR code or phone number and review connection and sign-in status. This uses unofficial automation and depends on current benefits, running services and network conditions.
Use your business information and number to access WhatsApp Business API through Alibaba Cloud ChatApp. Templates, messaging windows and fees follow actual upstream platform rules.
Only two routes are shown. No channel selection, rule agreement, scan, or connection occurred. Web uses unofficial automation; ChatApp requires the user’s business, number, and channel conditions.
Translation, understanding and reply preparation
Actively choose message translation, conversation analysis or reply suggestions. After reviewing the draft, keep checking specifications, quantities, delivery dates and commitments.
One message. Four stages.
Click Linbo to translate, analyze, edit a draft, and try a simulated send.
Hi Emma, happy to help with your bottle enquiry.
10:28Hi, could you quote 1,000 stainless steel bottles? Delivery to Hamburg. Please confirm the production lead time.
10:29Keep the customer's original words. Choose an action above to see the result here.
Fictional inquiry and local examples. Editing, checking, and simulated sending happen only on this page.
1,000 stainless steel cups, bound for Hamburg. Product, quantity, and destination together. You still confirm the production lead time.
1,000 stainless steel bottles · Delivery to Hamburg
Capacity, packaging, and trade terms are not yet specified. Clarify these questions before preparing a quotation.
Keep original words, media, and history in your own conversations. First understand the requirements the customer has clearly stated.
View featuresSelect messages yourself and request translation or analysis separately. Check numbers, specifications, and dates against the original.
View featuresPrepare the next response around the current conversation. You read and edit the draft; generation does not mean it has been sent.
View featuresReview the recipient, language, and business commitments. Browser reply checks also require installation, authorization, and page compatibility.
View featuresActual use requires authorization of your own account, channel and AI configuration, plus applicable entitlements and points. Web uses unofficial automation. ChatApp is subject to templates, the 24-hour window, and channel fees. Single-message translation processes the selected message. Reply suggestions may include context from up to eight recent messages, with up to 800 characters each. Analysis may synchronize CRM first, then prepare a draft requiring human confirmation. Browser reply checks require separate installation and authorization.
Individual translation uses the selected text. Reply suggestions reference up to 8 recent messages, each truncated to 800 characters. Message analysis can synchronize customer records first, then prepare a draft for human confirmation.
Edit using actual product facts and decide which part to use. AI configuration and credits must be available. Understanding messages, editable drafts and actual sending are confirmed separately.
The browser extension can translate selected incoming messages, prepare replies and check for accidental Chinese text in WhatsApp Web. Installation, authorization, page compatibility and actual-account acceptance are required. It is not an official WhatsApp plugin.
Web translation and reply checksConversations, templates, history and status
Confirm which of your accounts you are using before viewing its messages, media and history. If the contact is unmatched, check the number and company before adding communication to a customer under your permissions.
The real screenshot shows 0 channels, 0 conversations and no signed-in account. It does not prove a connection, synchronization or sending.
Explore customer-linked communication
Currently 0 channels and 0 conversations, with no own WhatsApp account signed in. Service-status marks do not prove account connection. No simulated customer messages or actual sending occurred.
For ChatApp, prepare templates, variables and media under upstream rules and review actual approval results. Check drafts, pending content and sending status separately. A prepared template is not a sent message.
The template screenshot has no actual channel or template draft. The editor contains a default example and does not represent upstream approval.
Template and draft counts are 0, and no channel is selected. The editor shows the original example. No saving, AI call, review synchronization, or Meta submission occurred. Template approval is not implied.
Find saved records in archives and review processing status through the actual channel. Provider acceptance, delivery receipts and customer replies have different meanings. Keep checking actual states and times.
The current archive screenshot is an empty state with no records. Actual messages and receipts require account authorization, running services and publicly reachable callbacks.
No archive records or tasks exist; only the original entry point was opened. No real conversations synchronized, files saved, or messages sent. History archival completion is not established.
See these highlights
Useful capabilities are found in each specific task.
01 / Explore more details
Summaries, highlights and labels help you understand the current email.
Real received screen of a public service notice. The body was still loading during capture. Only subject and summary are visible; full text or attachment reading success cannot be inferred.
Features in concrete numbers
Number of scenario options in the email-writing interface.
Features in concrete numbers
Writing settings. Actual generation depends on models, services and account conditions.
02 / Explore more details
Bring identity templates and additional instructions into reply drafts together.
Only the additional-requirements field is shown, without sender identity or account selection. No analysis, reply generation, or email sending occurred.
03 / Explore more details
Recipients, body text and the basis for contact each have a place to check.
No recipients selected; basis, subject, and body are empty. No list preflight, task creation, or sending occurred. Existing information counts do not indicate contact permission.
Features in concrete numbers
Adjustable writing directions. You still check the final draft.
Numbers come from current feature definitions or real interfaces. Workflow numbers explain the presentation on this page; demonstration data is not a promise of efficiency or business results.View all features and conditions
Factory introductions, inquiry replies and sample follow-ups each need different priorities. Choose scenario, language and tone first, then add product specifications and delivery conditions. 17 scenarios × 18 languages × 10 tones.
Explore this featureScenario × Language × Tone
The combination count multiplies option counts. It is not a count of templates, models or validated outputs. Drafts still need human review.
Take a closer look
Introducing a factory, replying to an inquiry and following up on samples each need a different focus. Choose a scenario, language and tone, then add actual product facts.
This counts option combinations, not templates or verified generated results. Actual drafts depend on the model, information and account conditions.
First outreach emailEnglishFactory capabilities
Turn specifications, delivery terms and factory information into an email you can keep editing.
Original interface with initial outreach selected. No email has been generated. 17 is the current scenario count, not acceptance of model results or sending performance.
No recipients selected; basis, subject, and body are empty. No list preflight, task creation, or sending occurred. Existing information counts do not indicate contact permission.
View the sender, subject, and time in received-email details. Read body text and attachments through your own mailbox. Open Linbo beside the email to continue understanding and preparing a reply.
Explore email reading and Linbo separatelyRequest AI organization in the selected received-email details, then check the context in the body. Requires an available model and the current email body. Menu screenshots show action entry points only.
Explore email reading and Linbo separatelyRequest category and keyword-label suggestions beside the current email to help identify business matters. Check labels against the customer’s words. A visible menu does not mean analysis has run.
Explore email reading and Linbo separatelyRequest a Simplified Chinese translation of the selected email. Chinese content can also be organized into clearer Chinese. Verify product specifications, numbers, dates, and clauses against the original.
Explore email reading and Linbo separatelyChoose an existing sender identity or the current mailbox identity, add requirements, and generate an editable draft. The screenshot only shows the requirements field. Verify facts and commitments; sending requires separate confirmation.
Explore email reading and Linbo separatelyOrganize the current email and existing assisted results. Favorites does not call AI. Body text stays on the current page; conversations save only necessary length-limited metadata. After switching or ending a session, read from the inbox again as needed.
Explore email reading and Linbo separatelyRequest original-text highlights in the current received email, then verify lead times, quantities, and other conditions in the actual sentences. Requires a model and original content. Do not infer a closed sale from highlights.
Explore email reading and Linbo separatelyDesigned for everyday work
Summaries, labels and highlights use the current email. Check important numbers against the original.
Learn moreTranslation helps understanding. Reply drafts combine the incoming email with your product facts.
Learn moreCheck recipients, body text and actual status separately, then decide which email to send.
Learn moreFrom draft to sending task
Mailbox identity, list provenance, body text and task status each have a place to check.
Configure your own mailbox and test receiving and sending separately. Sender-identity templates explain who you are; outreach body templates explain what you want to say. After choosing templates, check the subject, body, attachments and recipient sources.
Enter the basis for contact before running pre-send checks. Recheck after changing the body or list. Monitor tasks under actual channels, quotas and sending intervals. Pause, resume and cancel controls affect only unprocessed tasks.
No recipients selected; basis, subject, and body are empty. No list preflight, task creation, or sending occurred. Existing information counts do not indicate contact permission.
Verify IMAP receiving and SMTP sending separately. Confirm which of your mailboxes is currently in use.
Check the list, subject, attachments and opt-out restrictions individually. Recheck after changes.
View pending, sent and exception records, distinguishing provider acceptance, delivery and customer replies.
Treat a completed draft as an email already sent.
View drafts, check results, pending queues and actual sending records separately.
Passing checks does not guarantee delivery. Actual messaging depends on mailbox permissions, channel availability and provider conditions.
Compare to see clearly
A comparison of feature uses. AI outputs are drafts, not messages already sent.
| The task | You provide | The software helps organize | You confirm |
|---|---|---|---|
| Summary | Current email body | A summary to help organize context | Check key context for completeness, then return to the original |
| Translation | Current email body | Chinese-language understanding assistance | Specifications, quantities, dates and transaction terms |
| Reply | Incoming email, identity template and additional requirements | Editable reply draft | Recipients, prices, delivery dates and the decision to send |
Explore every feature
13 features, with body text directly visible. Read real interfaces alongside process notes, or open individual feature pages for more detailed inputs, outputs and examples.
LDG-022
Handle customer communication in your own authorized account.
Configure, test, switch or delete your own email accounts. Receiving uses IMAP and sending uses SMTP. Actual provider permissions are required; a successful connection test does not authorize bulk sending.
Enter IMAP receiving and SMTP sending settings for your own email account.
Run connection tests and check provider requirements and authorization scope.
Switch or delete accounts as needed, then review the corresponding emails.
A successful connection test is not provider approval for bulk sending. Actual sending and receiving depend on the provider and account permissions.
Original current-account check crop. No credentials are shown or changed. Statuses do not mean all providers connect, bulk sending is permitted, or specific emails were delivered.
LDG-023
Start with editable wording and continue outreach using verified information.
Generate and edit outreach subjects and body text from product facts. Copy or transfer drafts into outreach, choose existing templates, add attachments and check recipient sources. Sender-identity templates differ from body templates; generating a draft does not send it.
Choose the email scenario, language and tone, specify the product and audience, then edit the generated subject and body.
Copy the content or bring the draft into the outreach workspace for further editing.
Add attachments or select existing templates as needed in outreach, then rerun preflight after checking recipient sources and the basis for contact.
The writing interface offers 17 scenarios, 18 languages and 10 tones. Generation requires actual model conditions; importing a draft does not send it. Attachments, existing templates and preflight are handled separately in outreach.
Original interface with initial outreach selected. No email has been generated. 17 is the current scenario count, not acceptance of model results or sending performance.
LDG-024
Read and prepare a reply around the same incoming email, keeping the customer context close at hand.
View received, sent and saved emails. AI provides 5 types of assistance: summaries, labels, translation, reply drafts and highlight marking. Drafts can include sender identity and requirements; edit before sending. Models and mailboxes must be ready.
Select an incoming email in the inbox and read the original and reply address.
Open Linbo beside this message's details and use summaries, tags, Chinese translation, replies or key-point assistance as needed.
Choose an identity, add requirements, edit the draft, then check and decide whether to send. Sent and favorite folders let you revisit existing content.
Real received screen of a public service notice. The body was still loading during capture. Only subject and summary are visible; full text or attachment reading success cannot be inferred.
Only the original menu beside received-email details was opened. No AI action or favorite addition was executed. Five AI actions require models and points; favorites does not call AI.
Only the additional-requirements field is shown, without sender identity or account selection. No analysis, reply generation, or email sending occurred.
No favorite emails exist and none were added. Complete body text and assisted results remain only on the current page. Conversations retain only necessary length-limited metadata, not permanent full archives.
Linbo's controls appear beside the selected incoming message. AI models, usage allowance and email must be ready. Check numbers, specifications, dates and commitments against the original item by item.
LDG-025
Keep a verification step for important information before sending.
Record the basis for contact, then check recipients, body text, attachments, blocks and unsubscribes. Recheck after changing content. Passing checks does not guarantee delivery or inbox placement.
No recipients selected; basis, subject, and body are empty. No list preflight, task creation, or sending occurred. Existing information counts do not indicate contact permission.
Explain the basis for contact and check the list's source first.
Check recipients, body, attachments, blocks and unsubscribes.
Recheck after content changes, then proceed through the actual channel.
Passing checks does not guarantee delivery, inbox placement or a reply.
LDG-026
Keep clear operational review records and do not send directly to unknown lists.
For operators to check the sources and processing basis of unfamiliar company lists. Users still confirm sending after review. This route is unavailable for lists of individuals or unknown entities.
Operations verify the source of unfamiliar company lists.
Check the basis for processing and eligible entities against the rules.
After review, the user still decides whether to proceed with sending.
This is an internal review process only. It is not available for lists of individuals or unknown entities and is not promised in customer plans.
Operations verify the source of unfamiliar company lists.
Check the basis for processing and eligible entities against the rules.
After review, the user still decides whether to proceed with sending.
This feature retains instructions and usage conditions but does not yet show actual business results.
LDG-027
Keep reviewing task states, exceptions and follow-on handling in one place.
Process queues using available channels, remaining quotas and sending intervals. View tasks, sent messages and exceptions. After receiving mail, replies can stop subsequent outreach. Actual channels still await operational validation.
Verify available channels, quota and sending interval.
Review pending, sent and exception states in the queue.
Once receiving is running, stop further outreach according to actual replies.
The live sending channel still requires operational acceptance. Provider acceptance, delivery and customer replies are different states.
An old rich-text attachment test task shows submission complete; unsubscribe and bounce lists are empty. This does not prove current queue delivery or customer receipt. No queue controls were executed.
LDG-028
Leave room to adjust remaining sending tasks.
View task history and progress, and pause, resume or cancel remaining sends. These controls apply to pending tasks; messages already handed to providers cannot be recalled.
Open task history and review current progress.
Pause, resume or cancel remaining tasks according to the actual situation.
Review the records to see which actions are still pending.
Open task history and review current progress.
Pause, resume or cancel remaining tasks according to the actual situation.
Review the records to see which actions are still pending.
This feature retains instructions and usage conditions but does not yet show actual business results.
Controls apply to pending tasks. This feature cannot recall emails already handed to the provider.
LDG-029
Carry opt-out and failure records into future work.
Save unsubscribed, bounced and blocked addresses to avoid contacting people who opted out. Reimporting does not automatically remove restrictions. Check actual statuses separately for provider acceptance, delivery and replies.
An old rich-text attachment test task shows submission complete; unsubscribe and bounce lists are empty. This does not prove current queue delivery or customer receipt. No queue controls were executed.
Review unsubscribed, bounced and blocked addresses.
Retain handling records and contact restrictions according to actual receipts.
Keep checking existing states when preparing another list.
Reimporting does not automatically remove restrictions. Final delivery and replies follow actual status.
LDG-030
Understand the usage conditions of each integration route separately.
View 2 routes: Web and Alibaba Cloud ChatApp. Web uses unofficial automation. ChatApp requires your business and number and is subject to templates, the 24-hour window and channel fees.
Review the WhatsApp Web and ChatApp integration descriptions.
Confirm your own business, number, templates and messaging-window conditions.
Prepare account authorization and channel configuration for an available route.
Web uses unofficial automation. ChatApp is subject to template rules, the 24-hour window and channel fees.
Only two routes are shown. No channel selection, rule agreement, scan, or connection occurred. Web uses unofficial automation; ChatApp requires the user’s business, number, and channel conditions.
LDG-031
Give account connection and subsequent management clear tools.
Pair by QR code or phone number. Switch, restore or delete your own login accounts, and configure and test connections as required. Entitlements and running services are needed; network configuration cannot guarantee an unrestricted account.
Pair your own account using a QR code or phone number.
Configure and test the network connection according to channel requirements.
Switch, restore or delete your own connected account when needed.
Benefits, running services and page compatibility are required. Network configuration does not guarantee freedom from account restrictions.
Only two routes are shown. No channel selection, rule agreement, scan, or connection occurred. Web uses unofficial automation; ChatApp requires the user’s business, number, and channel conditions.
LDG-032
Connect current conversations with those that already happened.
View conversations, media and history in your own account. ChatApp supports variable templates and upstream reviews; Web has no official template center. HTTP callbacks need public reachability. Use receipts to check delivery.
Open conversations and media from your connected account.
Prepare variable templates according to the channel and review upstream approval or receipts.
Revisit archived history and keep checking the corresponding communication.
Currently 0 channels and 0 conversations, with no own WhatsApp account signed in. Service-status marks do not prove account connection. No simulated customer messages or actual sending occurred.
Template and draft counts are 0, and no channel is selected. The editor shows the original example. No saving, AI call, review synchronization, or Meta submission occurred. Template approval is not implied.
No archive records or tasks exist; only the original entry point was opened. No real conversations synchronized, files saved, or messages sent. History archival completion is not established.
ChatApp and Web have different capabilities. HTTP callbacks must be publicly reachable, and delivery follows actual receipts.
LDG-033
Understand messages or prepare drafts for the needs of this conversation.
Select messages yourself for translation, analysis or replies. Single-message translation uses the selected text. Replies can include up to 8 recent messages of up to 800 characters each. Analysis can synchronize CRM first, then request drafts for human confirmation. AI configuration and credits are required.
Actively select the message you need to understand.
Request translation, analysis or a reply draft.
Edit against the original before deciding how to continue communicating.
This feature retains instructions and usage conditions but does not yet show actual business results.
Actively select the message you need to understand.
Request translation, analysis or a reply draft.
Edit against the original before deciding how to continue communicating.
Individual translation processes the selected text. Reply suggestions may include up to 8 recent messages of up to 800 characters each. Analysis can synchronize to CRM before requesting a draft. AI configuration and credits are required; people confirm the results.
LDG-085
Continue understanding and preparing communication alongside the current browser conversation.
Translate selected messages, draft replies and check unintended Chinese-language sends in WhatsApp Web. Requires extension installation, authorization, page compatibility and actual account validation.
Install and authorize the browser extension according to actual requirements.
Select an incoming WhatsApp Web message to translate or prepare a reply.
Check for accidental Chinese replies and review the content before deciding to send.
Requires extension installation, page compatibility, and actual account acceptance. This is not an official WhatsApp plugin.
Install and authorize the browser extension according to actual requirements.
Select an incoming WhatsApp Web message to translate or prepare a reply.
Check for accidental Chinese replies and review the content before deciding to send.
This feature retains instructions and usage conditions but does not yet show actual business results.
Understand before use
Actual messaging requires account authorization, provider connections and the relevant entitlements. WhatsApp Web uses unofficial automation; channel conditions are explained separately. It does not negotiate or confirm sales automatically.
This catalogue explains existing features and their conditions. Availability depends on the release, account permissions, service configuration and completed validation. Some items are internal-only or still await operational validation.
Other work to explore too
From an amount to a complete explanation.
Explore this product