Emanate Ray

Emanate Ray, Ray for short, is the AI that comes with the product. Wherever a page in Emanate can build something from a plain-language description, write a draft, search by meaning or answer a question about your data, Ray is the one doing it. It has one name and one mark everywhere, so you always know when you are handing work to an AI, and you can expect it to behave the same way on every page. Ray is not your personal assistant. The assistant you create in Home belongs to one person: it has a name you chose, an email address, a mailbox it reads and tactics it runs on its own while you are away. Ray belongs to the whole workspace and works on whatever is in front of you when you ask. The two are compared side by side at the end of this page, and the assistant has a page of its own: Your assistant.

​

How to spot Ray

• The Ray mark. A small ray glyph on a button or a section header. Pressing a button that carries it hands that one job to Ray: rewrite a column, build a search, generate an image, read a spreadsheet.
• A chat called Emanate Ray. A panel or tab with that title is a conversation. You describe what you want, Ray asks when something is missing, and the result takes shape beside the chat: a quote, a sequence, a workflow, a monitor query, a tactic definition.
• “with Ray” and “Ask Ray”. Buttons and placeholders such as Quote with Ray, Personalize with Ray, Refine with Ray, Draft with Ray, or Search contacts or ask Ray, all open Ray.
• Ray in the record. In the account drawer’s History tab, Ray’s recommendations sit in the same timeline as your emails and notes, marked as Ray. In Logs, the Activity view lists every action in the workspace by people, by Ray and by automations; a row that reads Ray for Sam means Ray acted on Sam’s behalf.

​

Two ways Ray works

• In conversation. Some jobs need a back-and-forth: shaping a quote from a messy RFQ, drafting a sequence, building a workflow, narrowing a monitor. These open a chat titled Emanate Ray. Ray keeps the conversation while the panel is open and applies what you agree on to the thing beside it. You can always edit the result directly instead of asking.
• In one press. Most of Ray’s work is a single action with a visible result: fill in a lead from a LinkedIn URL, rank a list by what you meant, personalize a sequence step, map a spreadsheet’s columns. The Ray mark on the button is the only sign, and the result lands where you can check it.

Either way, Ray writes and proposes. A person reviews, sends, submits or turns things on.

​

Where you will meet Ray

​

Inbound

• Quote with Ray (Demand, Quotes tab). Opens a chat titled Emanate Ray beside your quotes: Draft, look up, and edit quotes from this chat. Paste an RFQ, ask about a quote or describe a change. Ray reads the request, looks up the customer, resolves the parts against your catalog, searches your past quotes and stages a draft quote on the Quotes tab for you to review and submit. It follows your Knowledge Base and the standing sales rules in your Repository, and it needs an agent with quoting turned on to work from. See Quotes.
• AI Draft on a thread (Demand). On any conversation, AI Draft asks Ray to read the whole thread and write a reply grounded in your Knowledge Base and past emails. Once a draft exists you can ask Ray to change something: make it shorter, change the tone, add a detail. Ray edits only what you asked; you send it. From a contact’s drawer, Email Assistant does the same for a fresh email: say what you want to say and Ray writes it. See Reading and replying.
• Agent instructions (Channels). When you set up an email, voice or chat agent, the instructions editor has an Emanate Ray tab. Describe how the agent should behave and Ray writes the instructions in the other pane, revising them as you talk. See Channels.
• Workflows. Build workflow with Ray opens a chat that edits the workflow on the canvas as you describe changes. The Smart Router, which reads each incoming email and decides which branch it takes, carries Ray’s mark. For a Computer-Use workflow, describe the portal flow in plain English and Ray generates the steps. In a Proposal Workflow, Ray drafts the proposal document from the deal sheet you attach and the settings on the canvas; Edit with Ray revises it, and What Ray worked from lists the judgment calls it made. See Workflows.

​

Growth

• Ray Account Reviews (Accounts). Every weekday, Ray reviews each of your qualifying accounts and proposes one next step where it matters: a drafted email, a win-back, a signal worth a look. The week’s reviews sit on a calendar on the Accounts page; each day’s ring shows how many of that day’s recommendations you have acted on, and clicking a day opens the top picks and the full log. Nothing is sent without you. An admin turns the reviews on and decides what Ray may read (account history and profile, purchase history, conversations, active sequences, the buying committee, the web, reorder and inventory matching) and what it may produce (an email draft, a contact suggestion, a conversation summary, an open-order update, a renewal reminder, a keep-in-touch note), exactly one per account per run. The same dialog sets how many priority picks surface each day (1 to 50), a floor of win-backs among them, and How should Ray write it, standing instructions applied to every draft. With Account expansion on, Ray names a net-new person at the account and you confirm them before any sequence is created. Ray builds each rep’s voice profile from their own sent mail, so a draft written for you reads like you. A Ray account digest can be emailed to whoever should see the day’s recommendations, and the Account Watch tactic emails each rep the picks routed to them.
• Inside an account. The History tab lists Ray recommendations alongside your emails, notes and sequence events, and a Ray row opens the day it came from. Where the account drawer has an Insights tab, it opens on Ray’s nightly read of the account and the signals it found: replies owed, risk signals, late shipments, pricing moves, cross-sell ideas.
• Search or ask Ray (Leads, Accounts, Contacts). The search box on each list reads Search contacts or ask Ray. Typing filters the list as usual. Press Enter or the Ray button and Ray reads what you meant (Understanding your search…, then Ranking contacts…) and ranks the whole list by it. The Understood as chips show how it read your request; remove one and the list re-ranks without asking again.
• Quick fill from LinkedIn (Leads, Accounts, Contacts). Paste a LinkedIn URL when creating a lead, account or contact and Ray looks it up and fills in the record.
• Intelligence columns and Enrichment Review (Leads, Accounts). Columns such as Account Fit, Timing Signal and Priority Action are written by Ray from the enriched record; Regenerate, in a column’s header menu, asks Ray to write them again. When enrichment finds a field that differs from what you have, Enrichment Review in the record’s drawer marks it with Ray and offers Keep current or Accept enriched. See Enrichment.
• Expand. Describe the companies you want and Ray builds the search. Refine with Ray narrows a finished search in plain language (only companies with 50+ employees), and each match condition shows The rule Ray checks. The Net-new prospects Ray finds carry its mark. See Expand.
• Sequences. The builder has an Emanate Ray tab: describe your outreach goal and Ray drafts the steps, or pick a template and describe what to change. Personalize with Ray, on an email or LinkedIn step, has Ray research each prospect’s website at send time and then either fill a slot where you typed @Ray, enhance your copy with a couple of researched facts, or rewrite the email around the research while keeping your offer and call to action; with an ERP connected it can work an inventory fact into the copy, and Why Ray made this change explains each edit in the preview. In a campaign, Draft with Ray writes each issue from your brief against your live data; a catalog block offers Customize with Ray to tailor the catalog per company; and Ray Suggestions on the Reports tab diagnoses a finished sequence against your others. See Sequences.
• Monitors. The query builder is a chat with Ray. Say what you want to watch, answer its clarifying questions, and the monitoring query takes shape in the box beside it, where you can also edit it directly. Every event a monitor surfaces carries Ray’s confidence and a Show sources & reasoning button. See Monitors.
• Segments. While you define an ideal customer profile, Ray reads your accounts and answers with specific numbers and names, streaming its reasoning so you can refine as it goes. In the page editor, describe a change and Ray applies it. See Segments.
• Microsoft Teams. A sequence-reply notification in Teams carries a Draft with Ray link that opens the reply in Emanate with Ray’s draft already started.

​

Observe

• Intelligence. The whole page is a conversation with Ray: Ask Ray anything about your business data. Ray runs read-only queries scoped to your organization, draws charts, explains how it ranked things, and on a harder question researches several areas at once (your business data, live ERP, email, knowledge base and documents), showing each lane as it works. It sticks to analysis: ask it to write an email or build an agent and it says that lives elsewhere in Emanate, then offers a data question it can run instead. Under Schedules, any question becomes a standing search Ray runs for you daily, weekly or monthly, with each answer landing in its own thread and, if you like, in an email to anyone who needs it. See Intelligence.
• Logs. The Activity view is the record of every action taken in the workspace, by people, by Ray and by automations. Filter to Ray & Automations to see only what the AI did. See Logs.

​

Resources

• Business DNA. Enter your website and Ray reads it: your name and tagline, what you sell, your industry, your tone, your colours and logo. Everything Ray writes for your company afterwards draws on it. See Business DNA.
• Knowledge Base. Import & Analyse opens Data Import: drop in a spreadsheet and Ray works out what kind of data each sheet holds and proposes the column mapping for you to confirm. The Ray toggle on the search box searches drawings and files by what they contain, not just their names. See Knowledge Base.
• Repository. When the Repository is empty, Let Ray draft it has Ray read your order and quote history and draft a first set of standing sales rules for review. Once rules exist, Ray reviews them every weekday morning against what was actually invoiced and raises a suggestion, marked Raised by Ray, only when a number in a rule no longer matches what the market is paying. Each suggestion shows What Ray read and How Ray got this number. An approver accepts or rejects it, and a rejection reason is taken into account next time.
• ERP integration. When quotes are written into your ERP, Set up with Ray has Ray propose how each quote field maps to the ERP’s own fields, and What Ray mapped shows the result for an admin to check. Describe a rule turns a quoting instruction written in plain words into rules the ERP can apply, marked Written by Ray; they arrive switched off. With Match intelligently on, Ray works out the closest items in stock when nothing matches exactly. See ERP.

​

Home

• Tactics Builder. The one place Ray works in Home. Tell Emanate Ray what should happen and when, in the chat on the right, and it builds the tactic definition on the left for you to read and edit. Once you enable the tactic, your assistant runs it, not Ray. See Custom Tactics.

​

What Ray knows

Ray answers from your workspace, not from guesswork. Each surface draws on the sources that fit its job:

• Business DNA: how your company introduces itself, what it sells, how it writes. Behind sequences, segments, proposals and the messages Ray writes in your company’s name.
• Knowledge Base and shared documents: catalogs, spec sheets, price lists, FAQs, and the files your team connected from its drives. Behind quotes, draft replies and Intelligence.
• Your workspace data: accounts, contacts, leads, orders, sequences, monitors. Behind Intelligence, Account Reviews and the search boxes.
• Connected systems: the ERP and CRM records Emanate has synced, and live ERP lookups where an ERP is connected. Ray reads the synced copy, so a system that has not synced yet is a system Ray cannot see.
• The Repository: your company’s standing sales rules, which every quote and draft obeys.
• The page you are on: the quote, the thread, the account, the sequence step. Ray works on that, not on everything at once.
• Your sent mail, on the surfaces that write as you, such as Ray Account Reviews.

Corrections you give Ray in Intelligence are kept for Intelligence alone. They never steer the drafts your assistant writes, and your assistant’s standing instructions never change how Ray analyzes your data.

​

What Ray does not do

• Send email. Ray drafts; a person sends. Quotes are staged for review, and workflows and sequences go live only when you activate them.
• Change your data from Intelligence. Its queries are read-only.
• Look outside your organization. Every answer is scoped to your workspace.
• Run your day for you. Ray has no mailbox, no address and no tactics. The scheduled jobs Ray does have, Account Reviews, Repository suggestions and Intelligence schedules, belong to the workspace, are turned on by a person, and end in a proposal or an answer for a person to act on.

​

Ray or your assistant?

​

Next steps