GGrais beta · for WhatsApp, Telegram, LinkedIn, Instagram

Your intelligence layer for every conversation. For humans and AI agents.

Grais is an applied AI lab building the communication harness for humans and AI agents — memory, reasoning, planning, and execution. Superpowers when you drive the conversation; the last mile when your agents do.

Request accessSee how it works

Free during beta. Works in Chrome, Arc, and Brave.

Sarah Kim · WhatsApp
New tab
web.whatsapp.com
SK
Sarah Kim
online
Monday
Kicking off the pilot conversation 🎉 — excited to scope this with you.
14:02
Likewise. Sending over the draft scope doc after this call.
14:04
Got it — ping me once it lands.
14:05
Wednesday
Just sent the scope + pricing memo. TL;DR: 6-week pilot, two milestones, $18k total.
09:41
Reading through now. The milestone split is exactly what we needed.
10:12
One quick thing — can we revisit the timeline? My VP wants to see this before she signs off.
10:13
Totally. I’ll revise and send a cleaner version tomorrow.
10:15
Today
Hey — got a minute to align on next steps for the pilot?
10:38
Yep, go for it.
10:39
Before I loop in our VP on Tuesday, could you send over a revised timeline with the two milestones we discussed?
10:42
Also — is pricing from the March 14 note still current?
10:42
Type a message
Grais
Grais
Who do I owe replies to today?
Three people are waiting on you:
  • Sarah Kim (Northwind) — revised timeline before Tuesday.
  • Marcus Reyes — deck feedback, soft deadline EOD.
  • Jules Tanaka — waiting on your call with legal.
Sarah is the one with a hard deadline. Want to start there?
Yeah, catch me up on Sarah Kim.
You’ve been working with Sarah on a 6-week pilot since Monday. She runs partnerships at Northwind and answers to a VP named Priya who hasn’t been in the thread yet.
Quick recap of the last week:
  • Monday: kickoff, you promised a scope doc.
  • Wednesday: sent scope + $18k pricing across two milestones.
  • Thursday: she asked to revise the timeline before her VP signs off.
What’s she actually asking for before Tuesday?
Two things: a revised 6-week timeline with the two milestones you sketched Wednesday, and confirmation that the $18k pricing from the March 14 memo still holds.
Her VP is the real audience here — Sarah needs to forward something clean, not a back-and-forth. Want me to draft it?
How can I help you today?

Persistent memory across every thread, channel, and relationship.

Grais remembers who said what, what was promised, and what matters to each contact — then grounds every draft in the full history, not just the last message.

Sarah Kim · WhatsApp
New tab
web.whatsapp.com
SK
Sarah Kim
online
Monday
Kicking off the pilot conversation 🎉 — excited to scope this with you.
14:02
Likewise. Sending over the draft scope doc after this call.
14:04
Got it — ping me once it lands.
14:05
Wednesday
Just sent the scope + pricing memo. TL;DR: 6-week pilot, two milestones, $18k total.
09:41
Reading through now. The milestone split is exactly what we needed.
10:12
One quick thing — can we revisit the timeline? My VP wants to see this before she signs off.
10:13
Totally. I’ll revise and send a cleaner version tomorrow.
10:15
Today
Hey — got a minute to align on next steps for the pilot?
10:38
Yep, go for it.
10:39
Before I loop in our VP on Tuesday, could you send over a revised timeline with the two milestones we discussed?
10:42
Also — is pricing from the March 14 note still current?
10:42
Type a message
Grais
Grais
Who do I owe replies to today?
Three people are waiting on you:
  • Sarah Kim (Northwind) — revised timeline before Tuesday.
  • Marcus Reyes — deck feedback, soft deadline EOD.
  • Jules Tanaka — waiting on your call with legal.
Sarah is the one with a hard deadline. Want to start there?
Yeah, catch me up on Sarah Kim.
You’ve been working with Sarah on a 6-week pilot since Monday. She runs partnerships at Northwind and answers to a VP named Priya who hasn’t been in the thread yet.
Quick recap of the last week:
  • Monday: kickoff, you promised a scope doc.
  • Wednesday: sent scope + $18k pricing across two milestones.
  • Thursday: she asked to revise the timeline before her VP signs off.
What’s she actually asking for before Tuesday?
Two things: a revised 6-week timeline with the two milestones you sketched Wednesday, and confirmation that the $18k pricing from the March 14 memo still holds.
Her VP is the real audience here — Sarah needs to forward something clean, not a back-and-forth. Want me to draft it?
How can I help you today?

Reasoning you can watch, step by step.

Read the thread, surface the right memory, plan the move, calibrate tone. Every step is visible — nothing happens behind your back.

Marcus Reyes · Telegram
New tab
web.telegram.org
MR
Marcus Reyes
online
Monday
Sent the first-pass deck — need your eyes on slide 6 before the board call.
14:18
On it tonight. The ARR chart needs to match the Sep close, not August.
19:40
Today
Updated deck is on the shared drive. Slide 6 rewired per your note.
10:58
Also — can we push the board prep call 30 min earlier?
11:02
One more thing, I’ll owe you a punchy close line for the end 🙏
11:18
Message
Grais
Grais
What’s the status on the Northwind pilot?
Monday kickoff, Wednesday scope doc, Thursday she came back asking to revise the timeline before her VP signs off Tuesday. You’re on track — she just needs the revised version in writing.
Did we commit to any numbers I should stay consistent with?
Yes — $18k total, split across two milestones, from your March 14 pricing memo. The scope doc you sent Wednesday lines up with that.
Catch me up and then draft the follow-up using the pricing we agreed on March 14.
On it. Pulling the thread and the relevant docs first so the draft lines up with what you’ve already committed to.
Reading thread history
24 msgs
Pulling pricing memo (Mar 14)
Cross-checking scope doc
Checking calendar for Tuesday
2 holds
Drafting reply
Calibrating tone to Sarah
queued
Flagging anything risky
queued
Pricing in your Mar 14 memo matches what you sent her Wednesday — no conflict. Two of your three Tuesday slots are free if she wants to loop the VP in live.
How can I help you today?

You approve every word before it ships.

Drafts sit next to the conversation, never instead of it. Insert, edit, or regenerate — the approval boundary is always yours.

Priya Rao · LinkedIn
New tab
www.linkedin.com/messaging
PR
Priya Rao
VP Partnerships · Northwind · 2nd
Last Friday
PR
Priya Rao · 15:22
Hi — I’m Sarah’s VP at Northwind. She’s spoken highly of the pilot conversations.
You · 15:41
Great to connect, Priya. Sarah and I sketched a 6-week plan on Wednesday — happy to walk you through it.
Today
PR
Priya Rao · 11:02
Sarah shared your scope doc. Two questions before I sign off:
PR
Priya Rao · 11:02
1) Is the $18k inclusive of the onboarding week?
PR
Priya Rao · 11:04
2) Can we move the week-3 milestone review to a Friday? Mondays are tough on my end.
Write a message...
Grais
Grais
What’s the right tone for Sarah?
Warm but businesslike. Her last six messages use short sentences, no exclamation points, and drop pleasantries after the first line. Match that — anything chattier will read as off.
And the structure — bullets or prose?
Prose for the first paragraph (she’s going to forward to her VP), then one short line with the numbers. The VP will skim.
Write it.
Grounded the draft in the full thread (24 msgs since Monday), the March 14 pricing memo, and your calendar. Kept the tone warm but businesslike — same register Sarah’s been using.
Grounded in 24 msgs + pricing memo
Hi Sarah — good timing. Attaching a revised 6-week plan with the two milestones we sketched Wednesday (week 3: integration live, week 6: ROI review). Pricing from the March 14 memo still holds: $18k total, split across the two milestones. Happy to walk your VP through it live Tuesday if it\u2019d help — I\u2019ll keep Monday afternoon open.
Want me to tighten it, add a line for Priya directly, or switch it to a bulleted summary she can forward as-is?
How can I help you today?

Works where you already talk.

One sidebar, every inbox. Grais reads and drafts across the channels your work actually happens in.

WhatsApp
Live
Web & desktop threads
Telegram
Live
Direct chats & groups
LinkedIn
Live
Messaging & InMail
Instagram
Beta
DMs & business inbox
In development
G
Gmail
Threads & drafts
i
iMessage
Native macOS app
S
Slack
DMs & channels
X
DMs

The capability stack

Six layers of intelligence that work together to make every conversation more effective.

Memory

Persistent context across conversations, channels, and time. Grais remembers who said what, what was promised, and what matters to each relationship.

Reasoning

Understands intent, tone, and stakes. Analyzes threads to surface what needs attention and how to respond. Not just what to say, but why.

Planning

Breaks complex conversations into steps. Planner Mode maps multi-turn strategies for negotiations, follow-up sequences, and relationship-building.

Execution

Drafts replies, schedules follow-ups, and manages communication workflows. Always with human review before anything is sent.

Tone calibration

Adapts to your voice, the relationship, and the situation. Knows the difference between a first cold outreach and a long-running partner thread.

Trust and control

You approve every action. Local-first architecture keeps data on your device by default. Cloud sync is optional and encrypted.

Frequently Asked Questions

From the lab

Research-backed frameworks for communication psychology, persuasion strategy, and AI-assisted conversation execution.

Coordination

State the Expiry Condition Before a Temporary Exception Spreads

A communication protocol for teams that allow one narrow exception for now but need to keep it from turning into routine practice by stating when it expires, what remains out of scope, and who confirms resolution.

Continuity

Carry the Decision Proof Before Another Handoff

A communication protocol for teams that already have the authority decision but still need portable proof of what was approved, what bounds apply, and what the next owner should do so execution does not stall or reopen the debate.

Coordination

Escalation Triggers Under Authority Constraints

A communication protocol for blocked threads where the contained path is exhausted and only a specific authority can clear the next move, so the team defines the escalation trigger, decision ask, and proof before widening the room.

Coordination

Dependency Visibility Before Another Chase

A communication protocol for stalled threads where the visible owner cannot move because an upstream prerequisite is still hidden, so the team makes the dependency legible before chasing again.

Explore all research →

Changelog

0.10

Faster startup, steadier recovery, and smoother chat

0.9

More reliable cross-channel context

0.8

Cleaner drafts, clearer history across channels

0.7

Cleaner replies and smarter defaults

See what's new in Grais →

Build with us.

Grais adds the communication intelligence layer your agents are missing. Get access to integrate Grais into your agentic stack, or talk to us about what you're building.

Request accessTalk to the team