The always-on agent inside PostWyse and OpsWyse. It spots the moment, drafts the move and hands it to your team.
Scroll to follow one lead through both products
- Finding leads that fitOutbound
Sara Patel, Ridgeway, fit 96, and 11 more - Testing two subject linesCampaignsA64%B47%
- Finding the best slotCalendarMTWTFThursday, 9:15
- Reading the accountCall prep
Owen Hale, Harbor Clinics. Five sections, call in 20 min - Checking the dealPipelineNewQualified$4,800, Maya Chen
- Drafting a replyInbox
Hi Maya, happy to. Most studios your size start on Growth.
Needs your yes
Spots the moment that matters.
Unified Inbox All channels
Maya ChenCan we see pricing before the call?
Intent 84Re: renewal terms for next year
Quiet 14 days
Ines DuarteMentioned you in a post on studio ops
Trend
Tom OkaforIs this the tool Brightline uses?
Priya RamanBooked a demo for Friday
Why Wyse flagged this
- Asked for pricing
- Viewed /pricing 3 times this week
- Fits your ideal client: studio, 10 to 50 people
Waiting for Lena to approveNew 3
Pinecrest Vets
Kestrel Freight$80kFieldhouse GymsQualified 2
Studio Kiln$4,800Harbor Clinics$48kMeeting 1
Northwind Labs$120k
Mesa Clinics$36kTwo products. One brain in both.
One brand, one voice, over 20 distinct capabilities tuned per surface.
Content, SEO, social and brand intelligence.
surfaces15
CRM summaries, replies, priorities and Triage Mode.
surfaces
Fifteen content moves. One agent.
Five of them carry the most weight. Each one runs in the product today; pick one or let them play.
Palette
Type
Voice
Friendly challengerCompetitors and pricing
Pricing that grows with your studio
Subject, A/B
Drip, built in two clicks
Builder, templates, segments, tracking and Mailchimp import, inside Wysera.
capabilities and surfaces in PostWyse.
Every PostWyse move, by job.
Answer the comment, then hand the lead to sales.
One click drafts a reply from your brand guidelines, editable before it sends
Lead, reply, intent score, signals and source go to the CRM together
Fifteen CRM moves. One outbound engine.
The deals, the calls and the prospects. Wyse ranks, briefs and drafts; you approve.
Pricing for the team tier, sent Mar 12
Automation across four clinics
Renewal date, budget owner, who else they are seeing
30 minute demo, then a pilot offer
Start from the ROI sheet Owen opened twice
Wyse drafted for Sara, in your voice
Sara, saw Ridgeway moved RevOps in-house last quarter. Two specifics on how teams your size shortened their deal cycle, if useful.You approve. Wyse sends.capabilities and surfaces in OpsWyse.
Every OpsWyse move, by job.
Read the record, the thread or the week in seconds.
A narrative summary in the record drawer, enriched from the web
Current state, their asks, your commitments, open threads, next move
What moved, stalled, won and is at risk, and what to do Monday
Opinionated about how Wyse thinks.
A model, a temperature and an output shape chosen for each job. Bring your own Claude or Grok key and override the defaults per org.
How much Wyse may vary, by job
Temperature, 0 to 1Intent routing, voice extraction, filter parsing. No variance allowed.
Your key comes first
The order Wyse tries providers in, logged per workspace and user.The right model for each job
Chosen per surface, logged per org and user.All 10 AI routes. Voice set per-route in system prompts, not model choice.
Speed + cost-optimized for content routes. Logged per org and user.
Higher token budget for full brand-kit JSON. 100s timeout.
Org-level Claude key supersedes env. OpenAI supported via the same BYO slot.
drafted_by, reviewed_by and sent_by with timestamps, so any customer-facing draft can be audited end to end.Built so you can actually use it.
Three commitments we wrote into the system, not the marketing.
Train public models on your data.
Wyse learns per workspace to hold your brand voice. Nothing trains public models, nothing leaks between workspaces. Your workspace sees only your workspace.
Stamp every draft with provenance.
Who drafted, who reviewed and who sent, with timestamps. If Wyse wrote a line you can see it, and if you edited it you can see that too.
Send without a human in the loop.
Waiting for Lena to approveWyse drafts, ranks and suggests. A person on your team approves every customer-facing action. Autopilot exists, but it is opt-in, never the default.
Questions about Wyse.
The things people ask before they hand an AI access to their inbox and editorial calendar.
Wyse is the AI copilot built by Wysera. It runs inside both PostWyse (content, SEO, social, brand intelligence) and OpsWyse (CRM summaries, replies, priorities, Triage Mode). One brand, one voice, over 20 distinct capabilities tuned per surface.
OpsWyse runs on OpenAI GPT-4o-mini across all 10 API routes, with temperature tuned per task (0.1 for routing, 0.3 for narrative, 0.4 for email drafting). PostWyse runs primarily on Grok-3-fast for speed and Grok-3 for heavier work like brand extraction, with Claude as a quality fallback. You can bring your own Claude, Grok, or OpenAI key at the org level to override defaults.
No. Wyse learns per-workspace to stay in your brand voice, but nothing trains public models, nothing leaks across workspaces, and every AI draft carries its provenance (drafted_by, reviewed_by, sent_by with timestamps) so you can audit exactly what shipped and why.
Not today. Wyse is the AI surface inside the two products. That tight integration is what lets it act on real signals (content trends, trending mentions, deal activity, inbox threads) rather than generic chat.
General assistants give you a chat box. Wyse lives inside the specific surfaces where you work: the editorial calendar, the pipeline board, the email thread, the record detail drawer. It watches the moments that matter, drafts in your voice, and hands the next move to your team with full context.
Never on customer-facing work. Wyse drafts replies, posts, and moves with word-count discipline (replies under 120 words, cold outreach under 110 words) but a human on your team approves before anything sends. Autopilot is opt-in, never default.
Yes. Provider priority is: org-level Claude key → env Claude key → org-level Grok key → env Grok key → OpenAI (via the same BYO slot). Every call is logged per org and user for usage analytics and future billing.
Both. Narrative summaries and structured JSON outputs (priorities, next actions, classification) are batched. The table chat (AIGridChatbot) and row-generation use Server-Sent Events so you see the answer type. Email drafts are batched since you want to review the full draft.
Triage Mode is a keyboard-driven inbox-zero flow over Wyse-flagged records. The queue is Wyse picks unioned with stalled deals and due-soon records, minus anything in closed stages. One card at a time, keyboard shortcuts to act, approve or dismiss.
Yes. Each Wysera workspace gets its own tuning: brand voice, ICP fit, preferred channels, approval rules. Wyse in one workspace never sees or learns from another. Brand kits extracted by /api/ai/brand are saved per org so every generation stays on-brand.
It doesn’t live in a chat box. It lives in yours.
Already inside the calendar, the inbox and the pipeline, waiting for the next signal.
Meet the team