Role
Its department and position in the company, exactly like a human colleague.
The complete walkthrough
From an empty account to a company that runs.
This page explains Blivo the way you'd experience it: setting up your company, giving it structure, meeting your AI employees, watching work move, and running the whole thing as the owner. No mystery, no magic; just a system that works the way a company works.
Chapter one
You describe your company. Once.
Everything in Blivo starts with the owner's description of the business. Not a form for its own sake: every field here becomes context your AI employees use later. A company described well is a company that runs well.
Identity
The company's name and details. This is who your AI employees work for, and who customers hear when they reply.
Industry
What the business does. A trading company and a services firm need different instincts; the platform starts from yours.
Goals and vision
What the company is trying to reach. This shapes what the owner's overview treats as important.
Branches
The real locations. Work, customers, and AI employees are attached to actual branches, not a generic 'office'.
Departments
Sales, support, finance, operations: the departments that actually exist in your company, named the way you name them.
Positions
The roles people hold. Positions carry default responsibilities and permissions, so structure does the managing for you.
Products and services
What you sell, at what price. AI employees use this to answer questions and prepare quotes and invoices correctly.
Policies
The rules of the house: discount limits, approval thresholds, response expectations, working hours. Written once, followed always.
Knowledge
The documents and notes your team would look things up in: terms, warranties, processes, FAQs. Your AI employees read these before they answer.
None of this needs to be perfect on day one. Companies grow into Blivo: add a branch when you open one, a policy when you write one. The platform is built to be extended, not re-configured.
Chapter two
Your company, branch by branch.
Blivo's structure is not a metaphor. It is your organization, entered once and enforced everywhere: work, permissions, and reports all hang on it.
Company
The top of the tree. One owner, one set of rules, one place where everything comes together.
Branches
Your real locations. Each branch holds its own departments, its own customers' context, and its own view of the work.
Departments
The functions inside each branch: sales, support, finance, operations. Every employee, human or AI, belongs to exactly one.
Positions
The roles inside each department. A position describes what this person is responsible for, and what they're allowed to do.
Employees
The people and the AI employees, side by side in the same list. The system treats them as colleagues because that's what they are.
Your company has branches, departments, positions, and people. In Blivo, AI employees join that same structure: they belong to a department, hold a position, and work under the permissions you set. Their work is accountable, because it happens inside the organization, not outside it.
CompanyBranchesDepartmentsEmployees
This is what makes Blivo different from a chatbot: AI employees are part of the company.
Horizon Trading & Technology
Amman, HQ
Sales
DanaSara · AISupport
Omar · AIFinance
Lina · AIZarqa
Operations
KhaledHuman and AI employees sit in the same structure on purpose. When work is assigned to 'Sales', it lands with whoever is responsible for it: a person, an AI employee, or both.
Chapter three
An AI employee is an employee.
Creating an AI employee looks like hiring: it gets a name, a department, a position, and a job description. The difference is that its boundaries are enforced by the system, not by hope.
Responsibilities
What it owns: which conversations, which tasks, which preparation work. Anything not assigned stays out of its hands.
Context
The company knowledge, policies, and customer history it works from. It answers from your business's reality, not from guesswork.
Permissions
What it may do on its own: read records, draft documents, send replies. Everything else requires a person.
Knowledge
The company documents it consults, plus its own memory of what it learned working with your customers.
Collaboration
How it works with others: who it hands work to, who covers for it, and who it asks when it's unsure.
Workflows
The sequences it participates in: a new lead gets followed up, a won deal gets invoiced, an overdue payment gets a reminder.
Escalation
The exact situations where it must stop and bring in a person. This is not left to its judgment; the platform enforces it.
A real employee record
Every AI employee has a card like this in the system. Its work is visible, its usage is metered, and its record is permanent.
SaraSales
AI employee18Active leads
11Follow-ups today
3Quotes prepared
Current workFollowing up on quote Q-2026-0006
OmarCustomer Support
AI employee12Conversations
27Resolved today
2Waiting for approval
Current workAnswering a conversation about delivery dates
LinaFinance
AI employee4Invoices prepared
9Payments matched
1Needs approval
Current workPreparing invoice INV-2026-0005
Product visualization with sample data from the Blivo interface.
Chapter four
One request, from message to record.
This is a real trace of how work moves through Blivo, exactly as the system handles it. Every step below is enforced by the platform, in this order, every time.
A customer writes
The message arrives on a connected channel and opens a conversation under the customer's record, with their full history.
The AI employee receives it
The conversation is routed to the AI employee responsible for that channel and department.
It understands the context
It reads the request together with the customer's history, the company's knowledge, and the relevant policies.
It checks its permissions
Can it answer this? Can it act on this account? The platform verifies what this employee is allowed to do before anything happens.
It follows policy
The company's rules apply: what can be promised, what discount is allowed, what information can be shared.
It does the allowed work
Answers the question, updates the record, prepares the document: the work it is permitted to do alone.
It asks when approval is required
Sending a quote above the discount limit, issuing an invoice, anything sensitive: the work pauses and lands in a person's approvals queue.
A person decides
The owner or manager approves or rejects, in one tap, with the full context in front of them.
The action executes
Approved work proceeds exactly as decided. Rejected work returns with a note explaining why.
Everything is recorded
The request, the reasoning, the checks, the decision, and the outcome land in a permanent record under the AI employee's name.
Two everyday examples
A delivery question on WhatsApp
- A customer asks when their order will be ready.
- The support AI employee checks the order and the branch's pickup hours in company knowledge.
- It confirms the answer is within its permissions: factual, from the records.
- It replies with the pickup details in the company's voice, in under a minute.
- The conversation and the answer are recorded on the customer's history.
A quote that needs a human yes
- A returning customer asks for a price on a larger order.
- The sales AI employee drafts the quote with the right products and prices.
- The requested discount is above the policy limit for solo work.
- It prepares everything and requests approval, with the numbers laid out.
- The owner approves from the approvals queue; the quote is sent and recorded.
If a step fails: the channel isn't connected, the approval is rejected, the customer's question is outside its knowledge: the work stops honestly and a person is brought in. Nothing pretends to have succeeded.
Chapter five
What the owner actually sees.
Blivo's owner view is not a wall of charts. It's the small set of things a person running a company needs to know, refreshed as the work happens.
Important work
The deals closest to closing, the customers waiting longest, the work that matters this week. Surfaced because it matters, not because it's loud.
Exceptions
Anything outside the normal flow: an approval that's been waiting too long, a conversation that went quiet, a payment that didn't arrive.
Bottlenecks
Where work is piling up. If invoices are stuck with one manager or one branch's tasks run late, the overview says so.
Approvals
Everything waiting for a human decision, in one queue, with the context attached. Approve or reject in a tap.
Alerts
Usage thresholds, overdue follow-ups, channel problems: events that deserve attention, delivered as notifications in the app.
Opportunities
Leads that came in, customers who came back, deals that moved. The good news, visible too.
Performance
Response times, resolution counts, work completed per employee, human and AI alike. Numbers you can check, not vanity charts.
Moving now12 active work items4 conversations in progress2 workflows running
Waiting on people3 approvals with managers1 quote awaiting customer reply
Needs your decisionInvoice INV-2026-0005 ($1,240) ready to sendNew lead from WhatsApp needs assignment
Daily note: Sales follow-ups ran on schedule this morning. Two customers replied and were answered within minutes.
Managers see the same view scoped to their department. The structure you built in chapter two decides who sees what; permissions are inherited, not hand-wired.
That's the whole system.
A company described by its owner, an organization that mirrors reality, AI employees with enforced boundaries, work that follows rules before it follows instructions, and one honest view for the person in charge. Everything else in Blivo is this, applied carefully.
Free 14-day trial · No credit card · Your data stays yours