See how the systems work.

Meet your LeBitsi AI Employee. It works across Resolve, LeBitsi OS and the CRM, so routine work gets done while you stay in control.

Start on the Tasks page. Describe the job in plain words, pick a specialist, and click Add task. The Employee reads the live products, records every step, and writes you a report.

Routine changes, like setting a ticket's category, run on their own. Anything significant, like replying to a customer, waits on the Approvals page. Approve it, or reject it. Each approval works once, for that exact change.

You set the limits. The AI budget page caps how much AI it may use each day and per task. Permissions decide what it may do alone, with approval, or not at all.

And if you ever need it, Pause everything on the Overview stops all work at once.

That's your AI Employee: helpful every day, and always under your control.

Here's how to give your AI Employee a task.

Open the Tasks page. Under New task, write what you need in plain words, for example: which open tickets are at risk of breaching their SLA?

Choose a specialist. Service desk works in Resolve, Operations in LeBitsi OS, Relationships in the CRM, and the Coordinator looks across all three. Set the priority, then click Add task.

Open the task to follow along. Every step is recorded: which model thought about it, which tools it used, and what it found. When it's done, the report appears at the top.

Sometimes a task pauses: waiting for your approval, for tomorrow's AI allowance, or because it reached its per-task limit. The reason is shown on the task. Sort it out, click Resume, and it carries on exactly where it stopped. Cancel stops it for good.

You decide how far your AI Employee can go.

On the AI budget page, the daily ceiling is a hard limit on AI use. The critical reserve is kept back for urgent work, and Most one task may use stops any single task from running away with the budget. Save each change as a new version, with a note on why.

On Permissions, every action has a setting: runs on its own, needs my approval, or switched off. Routine changes can run alone. Significant changes, like replying to a customer, can never skip your approval.

Below that, Automation turns on the daily briefing, and can open a task for each breached SLA, up to a daily cap.

Finally, AI models shows which free model handles each kind of work. Nothing changes until you approve it.

Every change is versioned, so you can always see who changed what, and when.

Need help from the service desk? Raise a ticket in LeBitsi Resolve.

Click Raise a ticket at the top of the menu, and choose the kind of help you need. Something is wrong is for faults. Service is down or degraded raises an incident. And I need something is for requests, like a new laptop.

Give it a short title, and describe what happened. For an incident, add the impact, the urgency and the affected service. For a request, pick the request type and answer its questions.

Desk staff can triage straight away: set the priority, queue, category and who it's assigned to, and record who it's for.

Then click Submit. You get a reference number, and you can follow every update under My work.

Here's how to work a ticket in Resolve.

Find it under My work, Queues or Tickets, and open it. The buttons at the top move it along: Accept, then Start work.

The Triage card saves as soon as you change it, and Assign to me takes the ticket.

Under Conversation, write to the requester and click Send reply. Tick Internal note for a note only staff can see.

Keep an eye on the Service level card. First response and resolution show on track, at risk or breached, and the clock stops while you wait for a reply.

When it's fixed, click Resolve and describe the resolution, which the requester sees. Close it when they're happy, or reopen it if they're not.

When a service goes down, Resolve helps you run the incident.

Open the incident and set its severity, impact and urgency. If it's serious, click Declare major incident, and managers are alerted straight away.

Post status updates as you go, so everyone knows what's happening. For a governed recovery plan, click Ask LeBitsi OS for a mission, and the team takes it from there in OS.

Link related tickets, so duplicates are handled together.

When the service is back, record the resolution summary and the post-incident review, then click Save incident record. Every step is kept in the ticket's history.

LeBitsi OS runs significant operational work as governed missions.

The Control Tower shows every mission: those needing a decision, active, preparing and finished.

Click New mission. Start from a blank mission or a pack template. Name it, and choose the governance tier, which sets how many approvers it needs. Add the risk, the SLA deadline and a description, then click Create draft.

On the mission, build the case. The decision card holds the narrative, the recommended action and the execution boundary. Add evidence, which someone else reviews, and record simulation runs.

Then move it through Validating, Simulating and Review, ready for approval.

When a mission is awaiting approval, approvers record their decision.

Choose Approved or Dissented, and give a rationale. Any dissent blocks approval, and nobody can approve a mission they created.

Once it's approved, the team runs it. Record each action in the execution log, with its status.

While monitoring, record readings, so predicted and actual results sit side by side.

Before closing, add at least one learning note: what to calibrate or change next time.

The audit trail keeps every step, and it can't be edited.

The CRM takes a prospect from first enquiry to won deal.

Every enquiry starts as a lead. On Leads, click New lead. Enter the person, their organisation, product interest, source and enquiry, then click Create lead.

Open a lead to work it. On the Qualification tab, record the business problem, the requirements, the timeframe and who decides, then click Save qualification.

Opportunities move along the Pipeline. Drag a card, or use its stage menu, from New Enquiry through discovery, demonstration and proposal, to Won.

Every move is recorded with who made it, and only a manager can mark a deal Won.

Proposals in the CRM follow a clear workflow.

Create a proposal from an open opportunity, and submit it for internal review. A manager approves the pricing and content.

Then email it to the prospect, or mark it as sent. When they decide, record the acceptance or the decline. To change a proposal after approval, create a new version.

When a deal is won, the customer is created and onboarding begins: eight stages, from Agreement Confirmed to Operational Support.

Mark each stage in progress, completed or blocked, and say what's blocking it, so nothing stalls unnoticed.