H

PRIVATE AI AGENT

Enter Hype

Your conversations and long-term memory are protected behind a private access key.

H
HypePersistent AI Agent
Conversations
Hype’s TA account & outreach
Checking system…

HYPE v0.9F.5.1 · RESPONSE RELEVANCE GATE · NATURAL DIALOGUE · RELEVANT TRANSITIONS ONLY · OWNER-GATED ACTIONS

New conversation

Agent online
H

YOUR PRIVATE AI

What are we working on?

Hype can reason, remember durable context, use a curated HypeBPO institutional brain, search the live web when enabled, and use local tools across multiple steps.

HypeBPO BrainLive HypeBPO readCandidate Journey Monitor21-day Gmail backreadBrevo monitoringInbox work queueApplication reconciliationReconciliation review queueLegacy HBPO reference tracingControlled application recoveryBatch draft-onlyExact draft reviewApproval-gated sendRecommendationsPersistent memoryVoice mode
Voice mode starting… Mic waiting…
Hype can make mistakes. Important information should be verified.
Hype noticed something

PERSISTENT OBJECTIVES

Missions

Track saved goals and progress independently of conversation history.

Open the saved mission queue.

PHASE 2E.1.2.1 · ACTION POLICY VISIBILITY → ASK HYPE → GOVERNED ROUTING

Hype Recruitment Intelligence Center

Live operational intelligence over Recruitment Portal records, candidate journeys, communications, approvals, and Proactive health. Governed actions route into existing workflows; this view never becomes a new source of truth or authority.

Loading live intelligence…
Building the current recruitment picture…

RECRUITMENT MOMENTUM

Hype Proactive

Hype keeps attention on candidate replies and follow-ups that can move EXL applications forward. System diagnostics stay secondary unless they block recruitment work.

Loading proactive status…

PHASE 2D.2 · JOURNEY POLICY → THREAD BACKREAD → DRAFT-ONLY SCHEDULER

Candidate Journey Monitor

Hype monitors every active EXL journey, applies eligibility and contact-fatigue policy, and can now queue a maximum of two candidate-specific draft check-ins per scheduler execution. Each candidate is thread-backread first; stage-aware drafts are live-revalidated. Drafting never submits approval or sends email automatically.

Load the current EXL candidate journey snapshot.
Zero-write intelligence only · Owner/Recruitment Manager stage authority is preserved.
Contact — Stage Aware = verified Recruitment Application stage may be referencedContact — Stage Neutral = engage without asserting an authoritative stageHold — Contact Fatigue = progressive 24h → 48h → 72h spacing blocks repetitive outreachHold = recent reply, identity, delivery/consent, EXL wait, or terminal condition blocks routine engagement

RECOMMEND → DRAFT → REVIEW → APPROVE

Hype Approval Center

One governed view for stage-change recommendations and candidate-email approval requests. Owner decisions still happen in the existing HypeBPO Command Center Approval Requests workflow; Hype cannot self-approve or directly send.

Loading stage and email approval state…
Stage changes and candidate emails remain governed by Command Center Owner approval.

PHASE 2C.3 · PRIORITIZE → RECONCILE → BACKREAD → DRAFT

Recruitment Inbox Work Queue

Hype turns the 21-day Gmail + Brevo attention scan into one prioritized candidate-action queue and can suggest read-only application matches for unmatched candidates. Brevo remains supporting delivery/consent evidence, not an inbound inbox or recruitment-stage authority.

Building the recruitment inbox work queue…
Batch drafting creates Drafts only (max 5). Approval submission stays separate; sending always requires Owner approval.

PHASE 2C.3.1 · UNMATCHED → EVIDENCE → OWNER REVIEW

Candidate/Application Reconciliation Review Queue

Hype reviews current Inbox Queue items flagged NEEDS_APPLICATION_MATCH one candidate at a time. Strong, ambiguous, multiple, weak, and no-match results are grouped for Owner review. This queue is read-only and cannot link records, create applications, or change stages.

Build the reconciliation review queue to inspect unmatched candidates.
Chunked read-only review only. No automatic linking, application creation, stage mutation, approval, or email send.
Strong single = one very-high-confidence suggestion Multiple strong = Owner selection required No match = keep unmatched / request identifying details

PHASE 2C.3.2 · NO MATCH → SOURCE EVIDENCE → REQUISITION GAP

Application Gap Review

Hype reviews candidates with no Recruitment Application and checks candidate, referral/follow-up, and open approved requisition evidence one candidate at a time. This phase is read-only: it cannot create applications, link records, select requisitions, change stages, submit approvals, or send email.

Build the application-gap review to inspect missing Recruitment Application records.
Read-only classification only. Candidate/client messages are evidence only and never create stage authority by themselves. A future recovery defaults to Contacted unless authoritative backend evidence or an explicit OWNER/RECRUITMENT_MANAGER manual determination supports another stage.
Requisition identified = one strong open/approved requisition for Owner review Legacy recovery = referral/follow-up evidence exists but requisition is unresolved Needs details = candidate exists but evidence is insufficient

PHASE 2C.3.3 · LEGACY RECOVERY → REQUISITION EVIDENCE → OWNER REVIEW

Requisition Evidence Resolver

Hype ranks current open/approved requisitions using source-reference bridges, site, role/LOB, email-subject, client, and timing evidence one candidate at a time. This phase is read-only: it cannot select a requisition, create or link an application, change a stage, create an approval, or send email.

Build the requisition evidence review to inspect legacy recovery candidates.
Candidate/client messages are evidence only. An explicit OWNER or RECRUITMENT_MANAGER manual stage determination may be authoritative; Hype/Gmail/Brevo never self-authorize a stage.
Strong = one separated high-confidence requisition for Owner review Ambiguous = multiple plausible requisitions; Owner must choose after more evidence Weak = keep unresolved / request identifying details

PHASE 2C.3.4 · HBPO REFERENCE → SOURCE TRACE → EXACT BRIDGE REVIEW

Legacy Reference Resolver

Hype traces legacy HBPO-... references back through authoritative Applicant Lead / Candidate Referral / Follow-up / Candidate source rows, then checks campaign, public-job, and requisition bridges. This phase is read-only and cannot create or link applications, select requisitions automatically, change stages, create approvals, or send email.

Build the legacy reference review to trace unresolved HBPO source references.
Exact source/reference evidence can prove a bridge, but Owner review remains required. Candidate/client messages are evidence only; OWNER/RECRUITMENT_MANAGER manual stage determination may be authoritative.
Exact requisition = stored reference chain proves one Recruitment Requisition Source resolved = HBPO reference traces to authoritative source row but not one requisition Conflict / ambiguous = do not recover until Owner resolves identity or requisition evidence

PHASE 2C.3.5 · SOURCE VERIFIED → HUMAN REQUISITION → OWNER APPROVAL → RECOVER

Controlled Application Recovery

Hype can prepare a governed recovery only after you explicitly select one current Open + Approved requisition for a source-verified candidate. Preparing creates an Approval Requests row only. The application is created at Contacted only after Owner approval in Command Center.

Build the controlled recovery review to inspect source-verified candidates.
Hype never selects a requisition or infers a stage. Recovery baseline is Contacted. Owner/Recruitment Manager may later manually determine stage from reviewed direct evidence; Accepted Job Offer remains protected.
Source verified = candidate + HBPO source reference are proven Human selection required = choose one exact Open + Approved requisition Prepare approval = creates APR only; no application until Owner approves

INSTITUTIONAL KNOWLEDGE

HypeBPO Brain

Curated HypeBPO identity, architecture, workflows, policies, and operating standards. This is not live applicant data.

LONG-TERM CONTEXT

Hype Memory

Durable information Hype can retrieve in future conversations.