Signal
Spots the moment that matters.
Trends, mentions, intent scores on one side. Stalled deals, ICP fit, unread threads on the other. Wyse watches both.
intent scoring · pipeline priorities
Wyse is the always-on agent inside both PostWyse and OpsWyse. Over 20 distinct capabilities, one brand, one voice, tuned per surface. Drafts the move, ranks the next one, hands it to your team with context.
Wyse doesn't sit in a chat box. It runs the same three beats inside every surface. Content on one side, revenue on the other, the same loop each time.
Signal
Trends, mentions, intent scores on one side. Stalled deals, ICP fit, unread threads on the other. Wyse watches both.
intent scoring · pipeline priorities
Draft
Brand-kit aware. Word-limit disciplined. 0.8s per draft. Every line tagged with provenance before it leaves.
temp 0.3 – 0.4 · brand-kit aware
Handoff
One click pushes the lead to Leorix with full context, or creates a task from the next-action. Nothing sends without a human.
Leorix push · create task
Wyse inside PostWyse spans the full content loop, from detecting a lead on X, to the AI Content Planner nothing else in marketing has, to Wyse Embed knowing your whole business, to Wyse Campaigns shipping email like Mailchimp without leaving Wysera.
Every detected lead (from mentions, inbox DMs, and form submissions) gets a 0–100 intent score from engagement signals. Company, role, platform source, original message, the signals that contributed.
Crawl any site. Wyse extracts the full kit: palette (hex), fonts, voice, archetype, competitors, pricing. Grok-3 with a 100s timeout.
Palette
Type
Fraunces
Inter · body
Archetype
Friendly challenger
Voice: direct, warm
POST /api/ai/brand · Grok-3
An AI-native planner you won't find anywhere else in marketing. Wyse reads your brand voice, search demand, trending topics and past performance, then proposes a full monthly map and auto-schedules every slot across every channel.
30-day map · auto-schedule · learns what lands
Drop one embed on any landing page. Wyse becomes your AI support and sales rep, trained on your content, brand voice, pricing and FAQs. Leads flow straight into OpsWyse.
One embed · full brand knowledge · leads hand off to CRM
Drag, drop, ship. AI drafts the subject in your brand voice, Wyse picks the send time, A/B tests what headline lands, and drip flows you build in two clicks. Replaces Mailchimp, Brevo, and Mailerlite without leaving Wysera.
Brand-aware drafting · CRM-aware audiences · runs inside Wysera
Subject
The 3 hours you waste every Monday
Open
64%
Click
18%
Reply
4%
One click drafts a contextual reply using your stored brand guidelines. Editable inline before sending.
Grok-3-fast default
Lead + reply + intent score + signal breakdown + source platform, bundled and pushed to the CRM in a single call.
POST /api/crm/leorix/push
Per platform, per content type, enriched with Semrush search volume and difficulty on every keyword.
POST /api/ai/generate
Wyse returns a JSON list of content ideas for any topic or keyword set. Each includes title, description, type, and tags.
Analyze
URL in. Company, industry, target keywords out.
Discover
4 competitors with strengths, G2 reviews, pricing.
POST /api/ai/competitors
Wyse suggests, Semrush enriches each with volume, CPC, and difficulty so you don't guess what ranks.
Tracks where your content surfaces in each model's answers, not just classic Google SERP. AIO and GEO coverage out of the box.
publishWorker ships scheduled posts with native schedules per channel. No copy-pasting across six apps.
listeningWorker pulls brand mentions and trending topics. The raw feed the Agent reads to score intent in production.
Worker: listeningWorker
metricsWorker syncs engagement from every connected platform. Analytics isn't a tab you switch to. It's ambient context for the Agent.
Worker: metricsWorker
Lead feed, filters, triage, draft, handoff to CRM
One-click entry to the Agent from anywhere
Invoke the Agent from any DM or comment
Score and hand off captured contacts to Leorix
Draft posts in bulk, queue every channel
Wyse inside OpsWyse is a cross-surface copilot. It ranks the pipeline, drafts the call prep, and runs the new Wyse Outbound engine, finding leads from your ICP, our 1M-record database, your Apollo key or our Chrome extension, then auto-pitching each one based on personality.
Up to 50 open deals in one call. High / medium / low urgency, with a dedicated bucket for anything 14+ days silent. Cached 15 minutes on the dashboard.
Terse, fixed-shape brief in the record drawer before every call. No filler, no reshuffling.
Where we left off
Pricing for the team tier
Their stated interest
Scaling automation across ops
3 questions
Renewal · budget owner · competitors
Goal
30-min demo → pilot offer
Opening angle
ROI deck shared Mar 12
/api/ai-summarize · call_prep
Wyse reads your company, infers your ICP, then pulls a matched list from our built-in million-record database, your Apollo key, or our Chrome extension scraping any page. Every lead gets a personality read and an auto-drafted pitch in your voice. You approve. Wyse sends.
Pulled from your ICP · enriched · pitched · queued
Sara Patel
VP RevOps · Stride
Marc Rivera
Head of Sales Ops · Lattice
Jenna Cho
Director Ops · Atlas Studio
“Sara, I noticed Stride moved RevOps in-house last quarter. Two specifics on how we cut deal-cycle 22% below.”
Narrative summary in the record drawer. Markdown-lite, 800 tokens max, enriched with the web.
/api/ai-summarize · summary
Current state · Their asks · Your commitments
Open threads · Suggested next move
/api/ai-summarize · thread_summary
/api/ai-summarize · weekly_recap
In-thread. First-name greeting. No fabricated facts. Your brand voice, drafted in 0.8s.
One clear next step. Zero buzzwords. Pulls the record title as the intended subject.
/api/ai-draft-reply · new
≤ 18 words. Plus the reason, ≤ 16.
One card at a time. The queue is Wyse picks ∪ stalled ∪ due-soon, minus anything in closed stages. Keys to act, approve, or dismiss.
Queue composition
Keys
/api/ai-voice · temp 0.1
SSE · temp 0.8
Summary and call-prep brief with tabs
One concrete next action + create-task
Inline 5-section thread brief
Draft reply with Wyse, editable before send
First-touch outreach drafting
Reply overlay with keyboard shortcuts
Daily deal ranker with template picker
Weekly recap narrative card
Focus today + Stalling (14+ days)
NL → grid actions, SSE streaming
Every AI call has a model, a temperature, and an output shape chosen for the job. No generic chatbot knobs. You can also bring your own Claude or Grok key and override the defaults per org.
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.
Intent routing, voice extraction, filter parsing. No variance allowed.
Grid actions, pipeline priorities. Shape-constrained output.
Summaries and single next-action suggestions. Controlled prose.
Replies and first-touch outreach. Slight variation for warmth.
Template row generation. Forces realistic spread across rows.
Every action writes drafted_by, reviewed_by, and sent_by with timestamps. Audit any customer-facing draft end-to-end.
publishWorker · 6 networks. metricsWorker · engagement sync. listeningWorker · mentions + trends. engagementSyncWorker · unified inbox.
Three commitments we wrote into the system, not the marketing.
We won't
Wyse learns per-workspace to hold your brand voice. Nothing trains public models. Nothing leaks between workspaces. Your workspace sees only your workspace.
We always
drafted_by · reviewed_by · sent_by with timestamps. Audit every AI touch end to end. If Wyse wrote a line, you can see it. If you edited it, you can see that too.
We never
Wyse drafts, ranks, and suggests. A human on your team approves every customer-facing action. Autopilot exists, but it's opt-in, never default.
Signed, Wysera
Effective · 2026-04-23 · v1.0
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.

Spin up a Wysera workspace and Wyse is already inside the editorial calendar, the inbox, the pipeline, waiting for the next signal.