Drafts built from your conversations, files, and notes

Beryl Compose writes replies, summaries, and outreach from your history with each contact, so you can start every message from a draft that you edit.

Drafts that quote your history with the contact

Before Beryl Compose writes a reply, a summary, or a follow-up, it gathers the messages that you exchange with the contact, the files that you share with them, and the notes that your team keeps about them. Its draft can name the last meeting, the objection that the contact raises there, and the deliverable that you promise them. Beryl drafts each reply to a client from your full conversation history with that client.

Draft every message from the history that you already have

The steps below show Beryl Compose drafting a reply, summarizing a document, writing to a whole group, and drafting in each contact's language.

What Beryl Compose drafts for you

Replies drafted from the whole thread illustration

A reply template gives every customer the same greeting and the same paragraphs. To make each reply personal, you will have to reread the thread and the contact's profile first, which takes time on every message.

Before Beryl drafts a reply, it retrieves the whole thread, the contact's profile, and the notes and files from your earlier meetings with them. The draft answers the question that the customer asks, mentions the feature from their last conversation with you, and matches the tone of your earlier messages, so you can edit it and send it.

A personal message for every contact in a group illustration

If you want to send a personal check-in to each of your top 40 customers, someone on your team will have to write 40 separate messages, so a team that is short on time can end up sending one email to all of them or skipping the check-in.

Beryl drafts a separate message for each contact in a group, mentioning details from that contact's account, such as the feature that they ask about, their most recently closed thread, or the colleague who works with them most. You can then review the 40 drafts and send each one from Channels.

Drafts in each contact's language illustration

Your contacts can write to you in French from Abidjan, in English from Lagos, and in Portuguese from Luanda, while your team writes in one of those languages. For every message in the other two languages, your team will have to use a translator or write it themselves in a language that they use less.

Beryl picks the language for each draft from your last thread with that contact. It also applies the local conventions for tone, greeting, and sign-off, so a message to a contact in Abidjan opens and closes the way that a French-speaking colleague there would write it.

When a partner sends you a scanned invoice, a screenshot of an error, or a slide deck, you will have to copy out the figures, the error text, or the action items by hand before you can write your reply.

Beryl extracts the text and figures from images, PDFs, and slide decks that someone attaches to a contact or a thread. When you ask for the invoice totals, the error text in the screenshot, or the three questions in the deck, Beryl returns them in a short summary with a link to the file.

Your Channels reports can show that three subject lines from last quarter earn 40% more opens than the rest. Unless someone works out what those three lines have in common, the campaign team will have to guess when they write the next campaign.

Beryl compares the open and reply rates of your earlier Channels campaigns, then drafts subject lines, body copy, and calls to action modeled on the campaigns that your audience responds to most. Each draft links to the earlier campaign that Beryl bases it on, so the team can see why Beryl suggests each line.

What changes when Beryl writes the first draft

Drafts in your own tone

Beryl matches each draft to the tone of your earlier messages and mentions the thread, file, or meeting that the contact cares about, so a reply from its draft reads like the rest of your correspondence with them.

Summaries you can verify

Because each bullet links to the page, message, or timestamp behind it, anyone who reads your brief can open the source of a point.

Personal outreach to a whole group

Each member of a group receives a message that Beryl writes from their own account history, which your team reviews and sends.

Reply in each contact's own language

Your team can reply to each contact in the language that the contact writes in, because Beryl drafts in that language.

How teams can use Beryl Compose

An account executive answers a prospect's pushback on price

A prospect pushes back on pricing in a Channels thread. Beryl Compose retrieves the full thread, the latest call notes in OneCloud, and the contact's profile in People, then drafts a reply that answers the price concern, mentions the feature that the prospect's champion praises on last week's call, and offers the discount structure that sales leadership approves for this account tier.

Result

The account executive edits Beryl's draft and sends it, working from the thread and the call notes that the draft already quotes. The prospect receives a reply about the concern that they raise, with the discount for their account tier.

An account executive answers a prospect's pushback on price

A consultancy sends each client a weekly status update

At the end of each week, the project lead sends a status update to every active client. For each client, Beryl Compose retrieves the deliverable files in OneCloud, the week's threads in Channels, and the project notes, then drafts an update that lists the work delivered, the work in progress, and the decisions that the client needs to make. The lead edits a sentence or two and sends it.

Result

Each week the project lead reviews one draft per client, because Beryl writes each update from that client's deliverable files and threads. Each client receives an update that names the deliverables that they are waiting on.

New customers each need a personal welcome in week one

The customer success manager sends every new customer a personal welcome sequence in their first week. Beryl Compose retrieves the contract, the pre-sales thread, and the contact's profile, then drafts a welcome email, a kickoff agenda, and a quick-start guide based on that customer's own setup. The customer success manager adds one personal sentence to each draft before sending the sequence.

Result

Each new customer receives onboarding material that describes their own setup from the first email. The customer success manager writes one sentence per customer, since Beryl drafts the rest of the sequence.

New customers each need a personal welcome in week one

20 minutes to brief a new lead on a 47-message escalation

An escalation thread with a large customer contains 47 messages from four weeks. The new support lead has 20 minutes before the call to save the account, so they ask Beryl Compose for a summary. Beryl writes one page on the issue, the commitments that the team makes, the blockers that remain, and the trend in the customer's tone, with each point linked to its message.

Result

The new support lead joins the call with each commitment and its source message on one page, so the lead can continue the conversation from the last step that both sides agree on. The lead can also open any message from the summary if the customer quotes it during the call.

20 minutes to brief a new lead on a 47-message escalation

Start each reply from your history with the contact

Ask for early access to draft replies, summaries, and outreach from the messages, files, and notes that your team keeps about each contact.