Search & Retrieval
Find prior work across connected sources without forcing teams to move everything into one repository.
// Platform
Bring scattered operating context into one working system.
Hey Zoran connects your storage, communication, website, inbox, project, and documentation systems, then puts that context to work through grounded assistants, workflow automations, decision intelligence, and structured outputs.
Embedded Assistants
Put grounded answers into Slack, support flows, and internal tools while keeping the source trail visible.
Web & API Delivery
Launch public or member-facing assistants through WordPress or custom API integrations where people already ask for help.
Email & Content Ops
Filter inbound email, draft replies, and generate templated content from your own knowledge base.
Decision Intelligence
Keep evidence, branches, accepted outcomes, and review history attached to decision work.
Planning Workflows
Extend captured decision context into linked planning flows with reusable prompts, gates, and review points.
// Connectors & Integrations
Connect the systems where the work already happens.
Bring storage, communications, project records, websites, and documentation into one working layer without flattening them into a generic dump.
Storage
- Google Drive
- SharePoint
- OneDrive
Communication
- Slack
- Teams
- Gmail
Project & Ticketing
- Jira
- GitHub
- Support or CRM exports
Documentation
- Confluence
- Notion
- Internal knowledge bases
Websites & APIs
- WordPress
- Member portals
- Public websites
- Custom API integrations
// Decision Intelligence
Keep the decision trail attached to the outcome.
The decision workflow keeps evidence, branches, review history, and the accepted outcome visible so teams can see what was proposed, what changed, and what was actually accepted.
Field
Accepted Outcome
Field
Branches
Field
Evidence
Field
Tradeoffs
Field
Assumptions
Field
Contributions
Field
History
Field
Next Stage
Decision #0041
Vendor Selection — Data Infrastructure
Nov 14, 2024 · Owner: Sarah K. (VP Eng)
Rationale
Chose Vendor B over A due to Canadian data residency requirements and stronger SLA terms.
Tradeoffs
Higher migration effort Lower long-term vendor risk
Constraints
Canadian data residency SLA ≥ 99.9%
Sources (4)
Inspectable evidence Source 1
Vendor B RFP
Source 2
Legal Review
Source 3
Pricing Sheet
Source 4
IT Security Assessment
// Search & Context
Search results with enough context to judge them.
Use dense retrieval and semantic search to find the relevant slice of organizational memory, then review the snippets and citations before you rely on it in an assistant, draft, or decision workflow.
Every result should make three things obvious
- Which sources were matched.
- Why they were relevant to the prompt.
- How confident the retrieval is before a team acts on it.
Find the last approved vendor residency decision for Québec infrastructure data…
Decision #0041 — Vendor Selection: Data Infrastructure
High confidenceLegal Review · IT Security Assessment
Canadian data residency and SLA terms drove the final recommendation after legal and security review were compared side by side.
RFP Response Library — Provincial Infrastructure
Relevant overlapProposal Archive · Pricing Matrix
Prior response language and pricing assumptions matched 78% of the current scope requirements.
Postmortem — Client Portal Rollout
Context matchSprint Notes · QA Summary
Approval bottlenecks and incomplete handoff notes were linked to release slippage across two milestones.
// Embedded Assistants
Start the lookup where the question is asked. Finish it at the source.
The assistant layer can live in Slack, on your site, or inside custom tools, but the answer still links back to the underlying material so the team can review it in context.
Customer support agents
Ground answers in help content, policies, and prior resolutions so support stays aligned to approved material.
For public, member, and logged-in experiences
Employee training chat
Bring onboarding guides, SOPs, and internal knowledge into Slack or other chat surfaces so teams learn inside the flow of work.
For enablement, onboarding, and frontline teams
Website assistants
Deploy chat-based help through the WordPress plugin or custom APIs without rebuilding your existing site architecture.
For WordPress sites, portals, and custom products
#
#delivery-ops
Source-linked review inside Slack
Nadia — 9:14 AM
/zoran find the last approved vendor residency decision for Québec infrastructure data
Hey Zoran
Most relevant artifact: Decision #0041 — Vendor Selection: Data Infrastructure. Final approval cited Canadian data residency, security review findings, and vendor SLA terms.
Legal Review Security Assessment Decision Artifact
// Content & Automation
Automate inbox and content work without losing your standards.
Use the same organizational knowledge layer to triage email, draft responses, generate templated content, run research, and validate copy before it goes out.
Email filtering and routing
Classify inbound messages against your knowledge base and workflow rules so high-value items reach the right human path faster.
Drafted replies and sending
Prepare response drafts or approved sends using customer context, policy constraints, and the right template for the situation.
Template-based content generation
Generate landing pages, emails, briefs, or support content from reusable templates and prompt recipes instead of starting from a blank page.
Research and alignment validation
Run web research mode and validate drafts against redlines, market positioning, and marketing standards before final review.
// Planning Workflows
Move from one-off decisions to linked, multi-stage plans.
Decision intelligence is extending into planning flows so earlier evidence, accepted outcomes, and constraints can stay attached as work moves through multiple decisions and stages.
In active integration
Linked stages
Carry evidence, rationale, and output state from one decision to the next instead of restarting each phase from zero.
Reusable recipes
Reuse prompts, templates, and validation rules by stage so planning flows stay consistent across teams.
Gates & approvals
Keep review points, ownership, and escalation rules visible as work moves from analysis to action.
Active integration
Multi-decision, multi-stage planning is being integrated with design partners for teams that need more than one-off outputs.
// Permissions & Privacy
Respect the systems of record instead of bypassing them.
Keep source permissions intact, make deployment and model choices explicit, and treat easier access as a reason for tighter controls, not looser ones.
Source permissions stay intact
If a user cannot see a document in the source system, that document should not appear in Hey Zoran search or review results either.
Customer data stays isolated
Each organization operates in an isolated environment, and customer content is not used to train shared models.
Deployment requirements stay explicit
Data residency, retention, and security requirements are handled as infrastructure decisions instead of vague promises.
Model choice stays open
Choose the foundation model setup that fits your team. Use your own key, start with OpenAI, Gemini, or Mistral, and switch providers or support self-hosted deployments without rebuilding workflows. Anthropic is coming soon.
// Next Step
Review the platform with your own workflows in mind.
Bring the systems that matter, compare how answers and decisions are captured today, and review what changes when grounded assistants and automation are easier to deploy.