Capture messages with the Chrome extension
Install from the Chrome Web Store, capture messages, update Cases, review replies, and manage approved accounts.
In this guide
- Install the published Chrome extension
- Account setup and capture in 0.8.1
- Channel, account and readiness
- Saved replies and wording
- Separate creation, update and send permissions
- Approve accounts before capturing
- Access notifications and blocked capture
- Control browser extension access
- Company email setup
- Use the side-panel workflow
- Keep drafts and recover a save
- Choose a capture channel
- Capture from WhatsApp Web
- Automatic capture in Capture
- Review source and access
- Troubleshooting
- Disconnect or change one account
- Find these controls in Workspace Settings
Install the published Chrome extension
Find the extension page from Chrome extension in the website menu, Capture with the Chrome extension in the homepage’s Capture step, or Yesoma Chrome extension under Conversation Channels.
Version 0.8.1 is published in the Chrome Web Store. Choose Add to Chrome, open Yesoma from the toolbar, then sign in with your own Yesoma account and approve the named workspace. No API key or Developer mode is required. Your workspace needs an eligible Business plan or higher; role, account and sending permissions still apply.
The extension page’s Capture, Recent and Reply screenshots show a sample workspace. They do not connect to your own account.
Watch the 45-second illustrated installation guide or read its transcript. The guide has on-screen instructions, English captions and sample screens, with no audio.
The production Chrome install prompt was checked on November 21, 2026: it names getyesoma.com and contains no workers.dev origin. Mail and chat website access is optional and requested separately when you enable capture. Review Chrome’s actual permission request before approving installation.
Chrome distributes Store updates. Check your installed version at chrome://extensions. If you have an older release, update through Chrome before following these instructions. A separately installed development copy does not receive Store updates; save its local drafts before removing it. Capturing an email or WhatsApp conversation does not connect that account for sending.
A loaded thread is the conversation currently open and expanded in your email service or WhatsApp Web. A structured capture keeps the message details, such as sender, date, and message reference, so Yesoma can check what is already saved. A local draft stays in this browser until you save it to a Case. A WhatsApp handoff prepares a reply in the original chat for you to review and send there.
What you can do in the published extension
- Capture a selection or review a loaded Gmail, Yahoo Mail, Outlook or WhatsApp Web conversation.
- Update the same Case with only new structured messages and keep available original dates.
- Find one Recent card per Case, refreshed when that Case is updated.
- Draft and review a reply, including its sender, recipient, subject and saved Case context.
- Let Owners/Admins choose whether Managers and Agents may capture, using their own accounts.
Account setup and capture in 0.8.1
Settings → Browser extension opens My accounts, showing only accounts assigned to you. Owners/Admins choose Team access to request or review other members’ accounts. A shared mailbox still needs a separate grant for each member. Expand How access and account changes work for the permission and notification rules, or the separate multiple-account section when disconnecting or revoking access.
Follow Add account → Verify or confirm → Enable capture → Ready. Each saved account shows its next step. Entering the same exact channel/address/member offers Continue existing setup, which opens the saved setup without requesting another verification code or creating another registration. An Owner/Admin can finish a previously verified pending setup with Enable my verified account and renewed authorization. Email verification and approval remain separate; an Owner/Admin’s own verified email or confirmed WhatsApp account needs no separate self-approval. A verification email is requested only when you choose Send verification code.
Back in the extension, Check status refreshes your account list, role/account access, Chrome site permissions and Yesoma reply sign-in. A newly approved account appears without reconnecting the workspace. Choose it and approve browser capture; refreshing status never enables capture or requests Chrome permission for you. Missing site permission or revoked access pauses the affected capture. Your local drafts remain available. Empty account lists explain whether to add an account, continue verification/approval or reconnect. Team accounts are not substituted for your own grants.
On opening, Capture selects the active tab’s supported channel when Chrome can expose its URL using existing site access. Otherwise it keeps the saved selection. You can switch manually; drafts retain their original account and Case. This only chooses the view: it does not inspect a conversation, grant access or send anything.
Capture setup errors stay beside the account controls after the short notification closes. Manage websites and longer explanations stay collapsed until opened. For a checked structured thread with no new messages, Case is up to date explains that every loaded message is already saved. Recapture when a new message arrives.
Channel, account and readiness
In Capture, choose Channel and Account beside each other. Only approved accounts for that channel are offered. Switching accounts asks for consent and checks access again; other channels and existing drafts keep their account bindings. Check status distinguishes capture access from your Yesoma reply sign-in. A signed-in status still requires checking the selected Case, recipient and sending connection before a send.
A structured capture shows the conversation with its recorded senders and dates. Edit captured text opens the text editor. If you edit that text, Yesoma warns that it may no longer be able to check for duplicate messages automatically. Long older titles are shortened for display without changing saved Case history.
For an existing Case, the action says Update Case · N new messages after a successful structured check. Case is up to date means no messages need saving. Add messages in Recent opens the same Case. A reminder is only scheduled if you explicitly add one under Plan the next step.
Saved replies and wording
In Reply, choose Saved replies to load the current channel’s published team replies. Select one to preview it, then Use saved reply to fill your local draft. Review remaining placeholders. Replacing existing text requires confirmation and keeps the old version in Kept reply drafts. Draft-only or unpublished templates are not shown. These text replies do not bypass Company WhatsApp’s reply window or submit Meta templates.
Write a reply, choose Shorten, Make warmer, Make clearer, Fix grammar or Match business voice, then Preview wording. Use revised wording applies the preview locally; it does not save or send. If you edited the draft after the preview, generate a new preview first. Wording tools use the same protected AI reply service as the platform, including its access and usage limits.
Separate creation, update and send permissions
An Owner/Admin opens Settings → Browser extension → Allowed extension actions, selects Manager or Agent, and chooses Create new Cases, Update existing Cases and Send replies, then Save action permissions. The main Browser extension access switch must also allow that role. Owners/Admins retain all actions; Viewers remain read-only. Eligible delegated roles retain their existing actions until restricted.
Permission changes apply the next time someone takes an action, including through an existing connection. A send already in progress may finish. Turning off new actions keeps saved Cases, drafts, and the records used to check earlier results. Normal Case visibility, assignment, account approval, and company sending rules still apply.
Approve accounts before capturing
The 0.8.1 release requires an approved account for Gmail, Yahoo Mail, Outlook and WhatsApp Web. Older website settings alone do not grant account access. Existing consented own Owner/Admin setups can enable when their account check is satisfied; revoked and unverified email accounts stay blocked.
- Open Settings → Browser extension → Approved accounts using your own Yesoma account. Choose the channel and exact mailbox address or WhatsApp number with country code. Owners/Admins have automatic role access. For their own setup, choose Add my email account or Confirm and enable WhatsApp. They authorize the exact account during setup, without a separate self-approval. Managers and Agents use Request account access for themselves; their capture role must first be enabled in Team permissions. Viewers and support-access sessions cannot request access.
- For email, verify the exact mailbox using Send verification code → Verify mailbox. The eight-digit Yesoma code expires after ten minutes; five attempts are allowed. Delivery is limited to one code per minute and five per hour per exact recipient, plus requester/account ceilings. An exact connected company Gmail mailbox can provide the evidence instead. Owners/Admins enable their own accounts automatically after verification. Sending a code alone does not enable an account.
- Manager and Agent accounts still need Owner/Admin approval. An Owner or Admin opens Team access, checks the account and member, confirms authorization and chooses Approve account. Adding an account for another member does not approve it automatically. Shared mailboxes and aliases need their own exact setup and a supported active-mailbox identity check. Approval does not expand supported layouts.
- Return to Capture, choose the channel, then Check status. Select your approved address/number in Account, confirm capture and allow Chrome site access. Manage websites offers manual setup and pause/change controls. The extension checks approval with Yesoma before reading.
WhatsApp numbers are Admin-confirmed. Yesoma does not automatically verify which number is logged into WhatsApp Web. Confirm the open approved account each time you choose Check loaded thread, Recapture or Prepare in WhatsApp. Automatic WhatsApp suggestions are paused; use explicit loaded-thread review. Confirming a number does not connect Company WhatsApp or create provider sending authority. Never enter a WhatsApp login or device-linking code in this Yesoma verification form.
To restore a revoked account, request it again above and complete a fresh review; its previous approval is not restored silently. Owners/Admins enable their own account after the new setup check; other members need approval again. If a connected Gmail mailbox was disconnected, use Send verification code to establish mailbox access again before asking the Owner or Admin to approve or recheck it.
Owners/Admins can Revoke access for a member/account. New captures and native handoffs stop, including new writes from older extensions. Saved Cases, local drafts and existing send receipts are retained. Recovery checks never send again; finish or cancel pending handoffs before changing accounts or access. Generic manual text keeps its existing Case permissions. Company email and Company WhatsApp keep their existing sending connections, recipient checks and approvals. Account approval is checked online; an unavailable check pauses the read.
Match the mailbox address to its channel
In Approved accounts, Yesoma checks recognizable email domains while you type. For example, a Yahoo address entered with Gmail selected shows Select Yahoo Mail and blocks Add my email account or Request account access. Choose Use Yahoo Mail to switch the channel while keeping the address and member, then review and check the authorization box again. The server repeats the check before a registration or replacement is saved.
Yahoo recognition includes regional domains such as yahoo.co.uk, yahoo.fr,
yahoo.com.au, yahoo.co.in, yahoo.at, yahoo.be, yahoo.cz and yahoo.com.ua,
plus myyahoo.com, ymail.com, rocketmail.com and y7mail.com.
Gmail includes gmail.com and googlemail.com; Outlook includes recognized
Outlook, Hotmail, Live and MSN domains and regional variants.
For a business or unrecognized domain, select the service where you open the mailbox. A domain alone cannot identify every company's email provider. Use the exact address: domain recognition does not combine aliases, prove ownership or replace mailbox verification, member approval or the active-account check. It does not add support for new webmail websites. Existing registrations are kept; an incorrect old channel entry can be revoked individually in Settings.
Access notifications and blocked capture
New account-approval and role-enabled emails link to account settings, the extension page's installation choices and this setup guide. These links are also included in the plain-text email. Choose your approved account in the extension and enable capture; approval alone does not grant Chrome site access or activate company sending. A notification describes the recorded change; check the current permission in Yesoma before continuing.
In 0.8.1, account approval and revocation create a member notification. This includes automatic activation of an Owner/Admin’s own checked account. Changes to the extension’s Manager/Agent role policy notify the active members of the affected role. Saving the same permission again does not create another notification. These notices start with new changes; old approvals are not emailed.
Yesoma tries to email the member’s verified Yesoma sign-in email, using its account-service sender. It does not send the notice to the captured customer mailbox or WhatsApp number. An in-app bell notification appears on refresh or navigation when in-app notifications are enabled. Account security emails are separate from Case email preferences. The fixed link opens Settings → Browser extension → Approved accounts; it never approves access by itself.
Permission changes take effect even if a notification email is delayed. Yesoma checks pending notices every two minutes. It retries only known failures from before the email service received a request, up to three attempts. An unclear sending result is held for review instead of being sent again. Use the current access shown in Yesoma rather than relying on an older email.
Blocked attempts explain the next step:
| Message | What to do |
|---|---|
| Verify this mailbox | Complete the email check in Approved accounts. |
| Confirm your WhatsApp account | Confirm the correct own account during setup. |
| Awaiting Owner/Admin approval | Ask an Owner/Admin to approve the member/account. |
| Access disabled for your role | Ask an Owner/Admin to enable your role in Team permissions. |
| Access was revoked | Contact an Owner/Admin; start a new setup/review if appropriate. |
Owners/Admins are not asked to approve their own verified accounts. A paused channel keeps its access explanation visible after reload. Your local drafts, saved Cases and existing receipts are kept. An unavailable online check pauses capture; a cached account list never grants permission.
Control browser extension access
Workspace Owners and Admins can open Settings → Team → Browser extension access, choose Manager and/or Agent, then Save extension access. Both delegated roles start off. Workspace Owners and Admins remain allowed; Viewers remain read-only. Each member connects using their own Yesoma account. A stale settings page must be refreshed before it can overwrite a newer policy.
Permission changes apply only after you save. Refresh permissions discards unsaved choices and reloads the saved settings. If settings cannot be loaded, check again before assuming access is on or off. The Agent checkbox controls Agents; older wording may call the same role “Responders”.
Changes apply to new connections and the next capture on existing connections. An in-progress save finishes before a policy change or observes the new policy; turning access off keeps saved Cases, exact receipts and local drafts. Re-enable access to check a locked result. Subscription and normal Case/reply permissions still apply: Agents cannot assign Cases, reopen closed Cases, update a Case assigned to somebody else or gain extra sending authority. Managers retain their normal assignment/reopening rights. Eligible teammates may capture follow-ups on their own or unassigned Cases. Internal support/governance Cases stay in Yesoma.
These controls apply to the current side-panel connection. General API keys and the legacy Store popup retain their existing scope/creator-role rules. Do not share an administrator’s API key; teammates must use their own approved connection.
Company email setup
Customer email sent through Yesoma requires your company’s Yesoma tag in Settings → Channels. If setup is missing, Set up company email opens those settings while your reply draft remains available to edit, copy and save. Ask a Workspace Owner or Admin to complete setup, then use Check reply availability and review the sender again. A connected Gmail mailbox can send supported manual replies without a tag; it does not provide a shared-address fallback when unavailable. Attachments and automated sends through Yesoma require the tag. Renamed or cleared tags keep receiving replies for the same workspace and cannot be reassigned.
Use the side-panel workflow
The following steps apply to the published 0.8.1 Chrome Web Store extension. Chrome 116 or newer is required.
- Open the toolbar icon and choose Connect to Yesoma. Your existing Yesoma sign-in opens in a separate window.
- Review the named workspace and click Connect this workspace. Workspace Owners and Admins can connect. Managers and Agents need their role enabled in Settings → Team. An active Business plan or higher is required. No API key needs to be copied.
- Select text and right-click Capture selection in Yesoma, or start a New capture and paste the message yourself. The side panel stays beside the page while you review the capture.
- Choose Create new case or Update existing case. A new case can use an existing customer or new contact details. To update, search and explicitly select a case. Owners, Admins and Managers must confirm reopening if it is closed, won or lost; Agents cannot reopen those Cases. Contacts are never merged automatically.
- Open Plan the next step to add an internal reminder, select its date/time in your local timezone and, with assignment permission, assign the case to an active teammate. This does not schedule a customer message.
- Choose Create case, Add follow-up, or Reopen and update case, then Open case. Recent shows your last 20 distinct saved Cases. Each Case appears once, with its latest save, Case number and source. Saving another update to the same Case refreshes that entry and moves it to the top; older captured messages remain in the Case history.
Find controls in the compact workspace
Capture, Recent and Reply stay at the top while the content scrolls. The workspace ··· menu contains Website connections, company email, access expiry and Disconnect. The save/review actions stay at the bottom. Expand Source and Case title or Plan the next step when you need those optional details. Always review the destination Case and new-message count.
Recent keeps one card per Case, including earlier captures. Its search filters your last 20 saved Cases locally. Reply opens the same saved Case; ··· opens its secondary actions. Equal titles can belong to different Case numbers.
Capture connected describes the extension connection. If a reply action finds that the website session expired, Sign in to send opens Yesoma. Sign in with the account connected to this extension, return and choose Check sign-in. Your local draft is retained. An uncertain send stays locked while you sign in; use Check saved result afterward. Signing in never sends a reply.
After merging Cases in Yesoma
The extension follows the surviving Case when you reopen the panel or refresh Recent. The merged Cases appear once, using the surviving Case number, title and customer. Reply, Open case and Add follow-up use that Case. Messages saved before the merge keep their dates and remain recognized during new-message checks, so recapturing does not add them again.
Unsaved follow-ups keep your text. Reply drafts also stay on this device; if both Cases had different local replies, expand Kept reply drafts to copy the other text. Review the surviving Case and recipient before sending. A previous send approval is cleared. A reply with an uncertain result stays locked to its original attempt: Check saved result never sends it again.
Finish recording or cancel a pending Original WhatsApp Web chat handoff before merging either Case. A merge is postponed until that handoff is resolved.
Draft a reply from the extension
After creating a case, selecting an existing case, or opening Recent, choose Reply in Recent, or Draft reply beside the linked Case. The Reply tab shows the case and customer. Stay signed into the Yesoma website as the account that connected this extension, in the same Chrome profile and workspace. Your current role and sign-in security are checked separately; a capture connection alone cannot generate or send replies.
- Choose Suggest a reply. Yesoma uses the saved Case conversation and relevant Business Brain information. If Your reply is empty, the generated text appears there immediately and stays as a local draft. Unsaved capture text is not included in generation.
- If you already have a reply, generating or regenerating keeps it unchanged and opens the new Suggested reply for review. Choose Use suggestion and confirm to replace your text, or keep editing your own reply. Review the explanation and any missing information, then choose Save draft to case. Generation does not automatically save your reply or send it. Oversize suggestions stay in the preview so you can shorten them without losing text. If the Case draft changed elsewhere, Reload saved draft asks before replacing your local work.
- If the Case has a saved customer email, send directly from the extension through Yesoma. Your workspace's configured email sender appears under From; the saved customer address appears under To. Capturing Gmail, Yahoo Mail or Outlook does not connect that mailbox for sending. Copy reply remains available when you want to use the original conversation.
- Choose Review & send at the bottom, verify From, To, Subject, the included conversation and the exact saved text, then Approve & send once. If the sender or saved reply changes, review it again before sending. Eligible WhatsApp Cases retain their normal reply flow. Permission, consent, connection and reply-window checks still apply. Use the full case for attachments or templates.
- If interrupted, choose Check saved result instead of sending again. Provider acceptance does not confirm delivery; open the case for delivery status. Write another reply starts a separate draft after an accepted send.
The subject includes the Case reference. Case context and included conversation shows saved external email and captured text that will be quoted, with Case-save UTC timestamps; any original captured dates remain inside that text. Internal notes and attachments are excluded. The quote includes up to the latest 20 eligible messages / 24,000 characters and shows an omission notice if shortened. A changed subject or conversation requires fresh review. Standard customer replies are matched through the accepted email and exact saved Contact, keeping an active Case intact even if another Case or duplicate-email Contact exists. The established closed-Case rule remains: replies within 72 hours reopen it; later replies create a linked continuation. Independent mail without a usable reference follows normal intake.
The first email sent from a captured conversation may appear as a new email thread if the original email's threading information was not captured. Its Case reference lets Yesoma connect later replies to the right Case. Earlier sent emails cannot be changed.
Use Check reply availability to refresh the saved information without losing your local text. If the Contact has no saved email address, add it in the full Case first.
Reply drafts and suggestions stay in local browser storage until cleared or the connection changes; they do not use Chrome Sync. Ten editable drafts are kept, while locked send records remain available for recovery. Closing, reopening, docking or popping out never automatically generates or sends a reply. Saved case drafts and messages remain subject to the workspace's normal retention.
Customer replies to a recently merged WhatsApp conversation follow the surviving open Case. The merged source stays archived. A deliberately separate newer Case and the normal closed-Case reply policy still apply.
Compare local and saved reply drafts
If Save draft to case or Review & send finds a newer saved draft, Saved draft changed shows that text while keeping Your reply unchanged. Saving and sending pause until you choose:
- Keep my reply keeps your current text and uses the displayed saved version for the next save. The other text stays under Kept reply drafts.
- Use saved draft asks before replacing the editor. Your previous local text stays under Kept reply drafts, where you can copy it back.
Choosing either option does not save or send. Review the recipient and text, then choose Review & send and approve once for a company reply. For an original WhatsApp Web reply, choose Prepare in WhatsApp, review the chat and sending account, and use WhatsApp’s Send button once. If someone changes the saved draft again, compare again. Reload saved draft also keeps replaced local text under Kept reply drafts. Locked or uncertain sends still use Check saved result; a draft choice cannot resend them.
Choose how to reply on WhatsApp
Original WhatsApp Web chat sends from the account currently open in WhatsApp Web. Check the sending account and the chat before clicking the native Send. When testing from a customer account, that message reaches the company as an incoming customer message. The Company WhatsApp route uses the company’s verified connection and saved recipient instead.
For a Case containing a structured WhatsApp Web capture, Reply → Send using offers Original WhatsApp Web chat and Company WhatsApp. The company route is available only when this Case has an eligible conversation on your workspace's connected number. A captured phone or chat does not create company eligibility.
- Original WhatsApp Web chat: keep the original chat active, with at least one previously captured message loaded. Review your reply, then choose Prepare in WhatsApp. An existing native draft is preserved. Review or edit the text in WhatsApp and click WhatsApp's Send button once. When its sent checkmark is verified, Yesoma automatically records the actual outgoing text and its original timestamp in the same Case. No extra Save or Capture is needed.
- Company WhatsApp: review the saved customer and message, then use Review & send → Approve & send once. The normal connection, role, consent, saved-number, reply-window and approval checks still apply.
A Web handoff stays locked while its result is pending. Check sent reply checks the original chat; Retry Case recording retries only the Case write. Neither inserts or sends the reply again. If you are signed out, sign back in and check the result. Cancel handoff works only before a native Send was observed; your WhatsApp edits are preserved. Write another reply becomes available after recording is confirmed. Another teammate's pending handoff must finish before starting one for the same Case.
Yesoma records an original-chat reply only after the extension observes it being sent in WhatsApp Web. The Case shows that it came through the extension. This is not a Meta delivery or read confirmation and does not open a company reply window.
The reply uses the original capture's message fingerprint, a saved code used to recognize a message, so capturing the thread again does not add it twice. If it is already saved, Yesoma uses that history entry. This process does not send attachments, account credentials, or raw chat/message IDs to Yesoma.
Completed records and unresolved handoffs remain available for checking a result. After starting another reply, up to ten earlier completed drafts are kept. Case access and record-keeping rules still apply. Older capture-only clients keep their existing copy workflow until updated.
Clear or cancel a capture
Choose Clear capture beside the draft selector, or Cancel capture below the form. Confirm to remove only the selected local draft, including its message, customer/case choices and next step. Other drafts, Recent and saved Yesoma cases stay unchanged. Cancel the confirmation to keep working. Clearing the last draft returns to New capture and remains cleared after reopening the panel.
Clear/cancel is unavailable while a save is running. If a save was interrupted, use Check saved result first. Remove local draft explicitly removes only the local recovery draft; it cannot undo a case or follow-up already saved.
Add a follow-up to an existing case
Choose Update existing case in Capture. Search by case number, subject, customer name/email/phone, or words in saved messages. Results default to the selected customer; clear that filter to search your workspace. Select the exact case and verify its customer, number and status. A new case number is generated only for Create new case. Updating a case keeps its number and returns it to the Inbox. Owners, Admins and Managers must explicitly confirm reopening a Closed/Won/Lost Case; Agents cannot reopen it through the extension.
Recent shows current Case status and the latest capture source/date. Search by title, customer or Case number. Its ··· menu contains Open case to read it and Add follow-up to start a new draft already linked to that case. Captures from this browser can retain their local saved source details: with the original conversation active, use Recapture loaded thread, review the preview, then Use updated thread. Otherwise paste/select the new text. Saving always requires your action.
For an unedited structured capture, Yesoma saves hashed message identifiers, fingerprints used to recognize messages without keeping their raw provider IDs. When updating the same Case through the extension, it adds only messages that are not already saved.
Already up to date means nothing changed: no message, reminder, assignment, or Case status was updated. This also works across extension connections to the same workspace. Older captures without fingerprints, and messages imported through other integrations, still need a manual duplicate check.
Editing the conversation turns it into a reviewed text capture, and all of that text is added. Check the existing conversation before saving edited text. Use Check saved result for an uncertain save instead of creating a new draft to try again.
See where a Recent capture came from
The 0.8.1 release shows Gmail, Yahoo Mail, Outlook, WhatsApp Web, Website or Manual capture beside each Recent item's date. The source label survives reopening the panel and recovering an interrupted save. Removing the source before saving makes it a Manual capture. The label never comes from the sender, message text or title.
Reload the existing unpacked test extension to use this update; do not remove it or clear its data. Earlier recorded captures also gain their labels from the recorded source. Older items without source evidence show Source unavailable. Install and update this release through the Chrome Web Store.
Identify the source in Inbox
The Inbox shows Via Yesoma extension beside captured-message times in Inbox, preview, and full conversations. Earlier messages can show it when a capture record was saved. In a conversation with several sources, each message keeps its own source; the Inbox row describes the latest incoming message.
Manual, Email, and WhatsApp remain channel labels. Capturing a conversation does not connect a mailbox or enable replies. Older messages without a saved capture record are not assigned a guessed source.
Keep drafts and recover a save
In 0.8.1, Pop out opens a movable capture window, Dock returns it to the side panel, and − hides/minimizes it. Drafts and the selected tab survive the move. This is a normal Chrome window, not an always-on-top website overlay. These controls and optional detection below are included in the published Chrome Web Store extension.
In the side panel, up to ten drafts are kept on your device. Closing and reopening the panel does not erase them. A new selection creates another draft instead of replacing an unfinished one.
If a save is interrupted, choose Check saved result. The draft stays locked while Yesoma looks up the original request. If it was not saved, that same request can be retried without creating a second case. Do not start a new capture to retry an uncertain save. If you reconnect to another workspace, check the original workspace's Inbox before discarding the old pending draft.
Choose a capture channel
In Capture, use the Channel dropdown to choose Gmail, Yahoo Mail, Outlook or WhatsApp Web. You see one account and its Check loaded thread action, suggestions and settings at a time. The menu shows pending message counts and which channels are Off.
Switching keeps your current draft, customer, source, Case and next step. Your Recent list and reply sender stay with their current Cases. The selection follows you when reopening, docking or popping out during this browser session. To set up an off channel, choose it first, then open Manage websites, enter the exact account and explicitly enable its access. Choosing it in the dropdown does not grant Chrome permission. Consent must be checked again after switching.
Clear suggestions removes only the selected channel's displayed suggestions. Other channels retain their waiting messages and remain enabled. The separate Stop all channels & clear detection data action still covers all websites after confirmation. The dropdown is unavailable while a capture save is running. Outlook continues to use explicit Check loaded thread review.
Capture from WhatsApp Web
- First approve the exact account in Settings → Browser extension. Then choose Capture → Channel → WhatsApp Web → Manage websites, review the consent and choose Enable WhatsApp Web. Approve Chrome's site access.
- Open the correct Web account and keep the chat in the foreground. Load the messages to include, then choose Check loaded thread. Review incoming messages, your replies and available dates. Confirm the customer yourself; phone numbers are not inferred from WhatsApp.
- To update a Case, choose Update an existing case, select the original Case and check its new messages. Only unsaved loaded messages are added after you approve the save. 0 new means the Case is up to date. For later replies, recapture the same loaded chat and accept the reviewed update.
Use Check loaded thread to review the current WhatsApp conversation, even if there are no suggestions. It checks message references, sender direction, and available dates before showing both sides of the conversation for review.
If the layout cannot be read, reload the extension at chrome://extensions, refresh WhatsApp, and check again. Keep the original chat loaded for later recapture. Hidden history, attachments, and text still in the compose box are excluded. The limit is 60 loaded messages and 10,000 characters.
Confirm the approved WhatsApp account before each loaded capture or new original-chat reply. Pause capture before switching accounts. Capturing does not connect the number for company sending. In Reply, choose the original Web chat or an eligible company WhatsApp connection.
Automatic capture in Capture
Open Capture and choose a Channel to find its suggestions beside manual drafts. There is no separate Suggestions tab. Manage websites holds the selected channel's settings: enter the exact Gmail or Yahoo Mail account, choose Likely customer messages or All incoming text messages, read and check the consent box, then enable the site and approve Chrome's permission. Each site starts off independently.
Open the conversation in a foreground tab. Detected messages offers new customer and business replies in a relevant loaded conversation, including short replies such as “OK.” A verified incoming message identifies the customer before your business reply can be offered. The toolbar badge and Capture tab show how many await review. An empty queue does not mean the mailbox has no new messages; choose Check loaded thread beside the account to check what is currently loaded.
Review both sides of a conversation
- Expand the older email messages you want, or load the relevant WhatsApp Web messages. Keep the original conversation in the foreground.
- Choose Check loaded thread beside the enabled account at the top of Capture. This works without a queued suggestion or keyword match. On a detected message, Include business replies and the loaded thread starts checked; choose Review thread. Uncheck it for Review message instead.
- Review one editable local draft containing incoming and business replies in message order, with sender labels and available timestamps. An incoming message identifies the customer; confirm the customer and case yourself.
- Choose Create case or Add follow-up only when the complete text and details are ready. Reviewing keeps message bodies local; the existing-case comparison sends only hashed message identifiers. Choose an existing case if another integration already imported the message.
Yesoma uses a verified incoming message and the loaded message references to recognize the conversation. Checking the same unchanged thread reopens its existing draft. A new message creates an updated draft without replacing your earlier edits. Single-message drafts stay separate, and the selected draft stays selected when you reopen or move the panel.
Add only new messages to a case
Choose Update existing case and select the correct customer and Case. For an unedited structured capture, New messages for this case shows new, already saved, and total message counts. The editable draft contains only the new messages. Full loaded conversation shows everything read locally.
Check new messages for this case refreshes the comparison. The comparison sends only hashed message identifiers and the selected customer/Case IDs to Yesoma, rather than message bodies. Add follow-up uploads the new text you reviewed. Yesoma checks for duplicates again when saving.
If every loaded message is already saved, saving is disabled and the case stays unchanged. Changing the selected case repeats its own comparison. Recapturing and applying a newer thread also refreshes that comparison. If you edited the text, Yesoma asks before replacing it with the checked thread. Edited text, older captures without fingerprints and messages imported by another integration still need manual duplicate review. Nothing is appended automatically.
Recapture after a new message
On an unsaved detected-message or thread draft, choose Recapture loaded thread with the original conversation active. Expand/load any newer messages first. The updated conversation appears in a local preview above your existing draft. Use updated thread replaces the message text; customer, case, title and reminder choices remain. Keep my draft dismisses the preview without changing your text. The preview survives closing/reopening the panel. If you edit the original draft after previewing, recapture again before applying it. Resolve the preview before saving; Save will explain this if a preview is still pending.
An unchanged thread does not append duplicate text. Recapture does not update an already saved Yesoma case automatically. Recover an interrupted save with Check saved result before any further capture; its original request stays locked.
Thread capture is limited to 60 messages and 10,000 formatted characters. Oversized or unverifiable threads are refused without truncation and existing drafts remain. Hidden/collapsed history, recognized quoted/signature text and attachments are excluded. The extension does not expand messages itself. Use manual selection or separate reviewed captures when needed. Account, permission, workspace, source tab/window or consent changes stop the read without replacing your draft. No additional Chrome permission is introduced.
Detection uses local English rules for pricing, booking, help, complaints and follow-ups; it can miss messages or offer personal ones. All-incoming mode skips the keyword filter. Automatic scans check at most 60 loaded, expanded messages, including business replies when an incoming customer anchor can be verified. A short new reply in an already recognized customer conversation is eligible without repeating a pricing or booking keyword. Unopened threads, background tabs, closed Chrome, attachments and compose fields are not monitored. Provider layout changes can stop detection; use manual selection if unsupported. In Gmail, expand an incoming message as well as the new reply so the customer can be verified.
Gmail/Yahoo must match the enabled account's current account control. Yahoo
supports only mail.yahoo.com and us.mail.yahoo.com, including the current
profile button with its menu closed. Identity is rechecked on each scan; an old
match or another mailbox in the account chooser cannot authorize capture.
Ambiguous senders/IDs and unsupported frames/layouts are skipped. WhatsApp uses
the Admin-confirmed Web account with your fresh confirmation for each loaded read. Phone
numbers are not inferred. Confirm all suggested customer details yourself.
The extension keeps up to 50 suggestions on your device. Suggestions older than 24 hours are removed the next time it checks or uses them. Up to 2,000 hashed fingerprints used to detect duplicates are kept for seven days and cleared as they expire.
Raw provider message IDs and private conversation URLs are not kept. Detected captures use the website's main address as their source. The thread details and preview needed to recapture a conversation stay on your device. Comparing an unchanged thread sends only message fingerprints for the selected Case. This does not detect duplicates imported through another integration.
Pause & remove access stops one site and removes its permission, retaining its queue. Clear suggestions empties the queue but keeps duplicate protection. Stop all channels & clear detection data clears all detector settings, queue and fingerprints. Disconnect/reconnect also clears detection state; reviewed drafts and saved cases are separate. Local connection expiry stops scans; server role/revocation checks occur when using the Yesoma API.
Chrome installs Store updates for the existing extension. Check the installed version at chrome://extensions; save local work and refresh the relevant email or WhatsApp tab if an update asks you to do so. Keep the existing Store installation rather than uninstalling it. A separately loaded development copy does not receive Store updates.
Review source and access
The side panel preserves the original selection separately from your edited message, along with the page title, source URL and capture time. Query strings, fragments and URL credentials are removed. Review the remaining URL path; use Remove source to omit the URL and title. Pasted messages have no source URL.
Manual capture reads your explicit selection/paste. Candidate detection reads customer and business replies in relevant threads locally only after site consent and permission; it uses the site's root URL instead of private conversation URLs. Existing-case checks send only hashed message identifiers and selected case/customer IDs; message bodies upload only when you explicitly save. Review thread, Check loaded thread and Recapture loaded thread also read your loaded outgoing replies as context in a local draft or preview. Neither mode monitors your clipboard. Drafts and the connection credential stay in the local Chrome profile, not Chrome Sync. Saved cases remain in Yesoma if you remove a local draft or uninstall the extension.
The extension’s capture-only connection expires after 30 days and cannot send messages, manage your team or change billing. Choose Disconnect to revoke it, and use Settings → Browser extension to manage approved accounts and access. If you previously used an API key with a legacy extension, revoke that unused key in Settings → API; deleting a local copy alone does not revoke it. See the Privacy Policy for data handling.
Troubleshooting
- Connection unavailable: check your internet connection and sign in to Yesoma again. If connection approval still fails, contact support; never paste a token or password into a support message.
- Approval refused: check your active membership, current agreement and eligible plan. Owners/Admins can connect; Managers/Agents need their role enabled in Settings → Browser extension → Role access. Viewers cannot capture. Connect with your own account outside support access.
- Customer not found: search their name, exact email or full phone number, then explicitly select a match or enter new contact details.
- Case unavailable: verify the selected customer and case. Deleted or other workspace and internal support/governance Cases are unavailable. Agents cannot append to another teammate's assigned Case or reopen Closed/Won/Lost Cases. Owners/Admins/Managers must confirm reopening; no status changes until saved.
- Old messages appear new: select the original Case before checking new messages. Structured unedited Gmail/Yahoo/Outlook threads compare against that Case's saved message IDs. Older unkeyed captures or edited text need a manual history check; do not save the full conversation again just to refresh it.
- Dates missing: expand the original message and recapture. Yesoma keeps source dates exposed by the supported page; it does not invent missing dates.
- Reply has no send action: add a missing customer email in the full Case, then check reply availability. If website sign-in expired, use Sign in to send, sign into the connected account and return to Check sign-in. Company email setup and normal permissions still apply; local text is kept.
- Save uncertain: check the saved result rather than creating another request.
- Connection expired/revoked: reconnect. Local drafts remain on your device.
- No suggestions: open a supported thread/chat in a foreground tab and check its status in Capture → Manage websites. Match your enabled Gmail or Yahoo Mail account exactly; use All incoming text messages if the English keyword filter is unsuitable. If the layout cannot be read, use Capture selection in Yesoma instead.
- Gmail asks you to expand a message: expand an incoming message from someone else as well as the new reply. Suggestions include business replies after a verified incoming anchor is found; collapsed message previews are skipped.
- Thread cannot be included: keep the original conversation active and check that its account still matches the one enabled. Expand older messages first. Threads over 60 messages or 10,000 formatted characters need separate captures. A failed read leaves the suggestion and existing drafts available.
- Yahoo account address unavailable: check the active address on Yahoo's profile button. If the page does not expose it, open the profile menu to inspect the account or use manual selection. A mismatch means a different or ambiguous account is exposed; Yesoma will not keep using an earlier match.
- Local extension updated: close the panel, reload the existing extension at
chrome://extensions, refresh open Gmail/Yahoo/Outlook tabs when safe, then reopen the panel. Keep the existing installation and its saved connection/drafts.
Open the extension page or contact Yesoma support.
Current Yahoo Mail captures
Check loaded thread reads the actual subject beside the scrolling conversation, original visible dates, and verified visible-card message IDs. The latest eligible external From email prefills a new capture for review; names alone never supply an address. The enabled mailbox address is treated as outgoing. The existing Case comparison shows only unsaved messages and disables Add follow-up at zero new. A sole previous same-thread/connection Case is restored unless you deliberately choose a new Case or another customer. Recapture preserves your selected Contact and never rewrites its saved address. Missing or ambiguous metadata needs review; older captures without message references are not automatically checked against past messages.
Platform agreement-signing notifications and payment receipts keep their existing Yesoma service identity and contact-permission checks. Company email setup applies to customer conversation replies, quotes, surveys and follow-ups; it does not block those platform document deliveries.
Capture from Outlook
The 0.8.1 Store release supports Outlook.com and Microsoft 365 web mail.
Choose Outlook in Capture’s Channel dropdown, then open Manage websites,
enter the exact Outlook mailbox address,
check the consent box, choose Enable Outlook, then approve Chrome's site
permission. Outlook starts off. The four optional hosts are outlook.live.com,
outlook.office.com, outlook.office365.com and outlook.cloud.microsoft.
The desktop app and other Exchange domains are not supported.
Open the conversation in the foreground, expand the messages you want to keep, then choose Check loaded thread beside Outlook. Outlook uses this explicit check rather than automatic suggestions. With the folder pane visible, Yesoma can verify one primary mailbox, or the selected mailbox among several, while the profile menu stays closed. If the address is hidden or ambiguous, show the folder pane or open the current profile menu and check again. Other accounts in the switcher and addresses inside messages cannot authorize the read. Review the customer, subject, available sent dates and text before saving.
Choose Update existing case and select the correct Case. The new-message check shows only messages not already saved through structured capture; 0 new means the Case is up to date. Recapture loaded thread previews later messages without overwriting your edits. Keep an original incoming message expanded so Yesoma can match the conversation. Older edited or unkeyed history still needs manual duplicate review. Outlook dates are kept when supplied; missing dates are not invented.
Unsupported layouts or ambiguous account/message metadata leave your draft unchanged. Use reviewed manual selection if your email layout is unsupported. Capturing Outlook does not connect it for sending. Replies use the saved Case's configured Yesoma sender: review From, To, Subject and context before approving.
Disconnect or change one account
In the extension, choose the channel, then Manage websites. Change account switches capture to another approved account in this browser. Choose the exact account and confirm consent again. Other channels and your current drafts stay. Disconnect account stops that account’s extension capture on all your browsers; it does not disconnect your workspace. Reconnecting requires setup and approval again. Pause this browser keeps the account approved. The workspace menu’s Disconnect workspace (all channels) stops this browser’s whole connection.
In Settings → Browser extension → Approved accounts, disconnect one or all your own accounts. Owners/Admins can revoke a single account, all listed accounts for a selected member, or all listed workspace accounts. Review the scope and count. Bulk actions apply to the accounts shown when reviewed; refresh to include newly added accounts. A changed account selection must be refreshed before saving.
Use Change account → Replace account to stop the old account and request its replacement together. Enter the new address or number and confirm. The replacement needs its own mailbox verification or WhatsApp confirmation, plus Owner/Admin approval for Managers/Agents. Existing proof never moves to a new address. Saved Cases, history, edited drafts and reply receipts are kept. Finish or recover an already-started reply before sending again; access may need restoring to reread the original chat. Company sending connections and role permissions are separate.
Find these controls in Workspace Settings
Settings → Browser extension brings Accounts, Role access and Allowed actions together. Team keeps a shortcut for older links. Search settings finds these controls by task. See Find and manage Workspace Settings for personal/workspace labels, Save/Cancel feedback and access-change confirmations.
More in Channels
- Setup10–15 min
Connect customer email
Set up company email, bring messages into Yesoma, and keep replies with the correct customer conversation.
Read guide - Setup10 min
Connect a website form
Connect your website contact form so submissions become inquiries in your Yesoma Inbox.
Read guide - Setup5 min
Connect WhatsApp to Yesoma
Request the limited assisted WhatsApp pilot and follow the setup and message-verification steps.
Read guide - Beginner4 min
Reply to a WhatsApp customer
Review, edit, save, and send a WhatsApp reply from Inbox.
Read guide - Beginner5 min
Why can’t I send a WhatsApp reply?
Understand a blocked or uncertain WhatsApp reply and find the next action to take.
Read guide - Beginner4 min
Understanding Sent, Delivered, and Read
Read WhatsApp delivery statuses and learn what to do when a result is uncertain.
Read guide - Setup3 min
Pausing and resuming WhatsApp replies
Pause outgoing WhatsApp replies while new messages keep arriving, then resume when ready.
Read guide - Beginner4 min
WhatsApp privacy and security
Understand WhatsApp access checks, private connection details, and customer-data protections.
Read guide - Beginner5 min
Use WhatsApp click-to-reply
Open the customer's WhatsApp chat with your draft ready to review and send.
Read guide - Setup10 min
Connect Calendly
Connect Calendly bookings to customer records and schedule follow-up reminders after meetings.
Read guide - Beginner4 min
Managed Messaging overview
Compare available messaging options and understand which connections require assisted setup.
Read guide - Beginner4 min
WhatsApp setup status
Understand the eight setup stages and whether your WhatsApp connection can receive or send messages.
Read guide - Beginner3 min
SMS setup status
Request an SMS connection review and learn what must be confirmed before it is enabled.
Read guide - Beginner3 min
Click-to-reply vs assisted vs connected
Compare replying in your own messaging app with using a connected channel in Yesoma.
Read guide - Beginner3 min
What happens after I request setup
Follow your assisted WhatsApp request from review to connection checks and setup completion.
Read guide - Beginner3 min
Instagram, Messenger & TikTok
Check which social channels are available and which have a waiting list.
Read guide
Was this article helpful?
If something was unclear or missing, tell us and we'll fix it.
Still stuck?
We'll help you get this working. Send us a message, or ask about Managed Setup.