← All UK guides

Business Rules for UK Service Firms

Reduce vague business rules enquiries in UK by guiding people towards clearer needs, timing and next steps.

Business rules are the explicit decisions a company has made about how it behaves: what it will offer, to whom, on what terms, and when a person must be involved. Written down and applied consistently, they keep a team aligned. When AI joins the team, they matter even more, because the system will follow them literally. Servadra holds a firm's rules in its Archon Book so that AI replies stay inside them.

What counts as a business rule

A business rule is a statement that can be checked. "We reply quickly" is an aspiration. "Every new enquiry receives a first response within fifteen minutes during opening hours" is a rule, because someone can verify whether it was met. Rules cover pricing policy, eligibility, service boundaries, response times, escalation triggers, wording that must or must not be used, and the conditions under which exceptions are allowed. Most firms already have dozens of them. The difficulty is that they live in people's heads, old emails and habits, and different colleagues remember different versions.

Why UK service firms feel the strain

Service businesses sell judgement, and judgement is exactly where inconsistent rules cause trouble. One adviser quotes a certain way, another offers a concession, a third declines work the first would have accepted. Customers notice. They compare notes, they ask why the answer changed, and trust erodes quietly. Growth makes it worse, because every new hire inherits a slightly different set of unwritten rules than the last.

Rules, policies and procedures are not the same

Keeping these separate prevents the common muddle in which a long policy document is mistaken for a set of workable rules. If a new colleague could not apply a sentence without asking someone, it is probably still a policy.

Writing rules that survive contact with reality

Begin with the decisions that are made most often, or that cost the most when they go wrong. For each, record the condition, the action and the owner. Add the reason, because a rule with a known reason is easier to maintain and easier to challenge sensibly. Mark the exceptions explicitly rather than leaving them to memory. Then review the set regularly; a rule that no longer matches how the business operates is worse than no rule, because people will either ignore it or follow it into a poor outcome.

Why AI raises the stakes

A human who knows the rules imperfectly will usually improvise sensibly. An AI that has not been given your rules will improvise too, but without any sense of what your business can honour. It might promise a start date you cannot meet, imply a service you do not provide or discuss a subject you reserve for senior staff. That is why governance matters: the rules need to be stated in a form the system works within, and the system needs to know when it has reached the edge of them.

How Servadra applies a firm's rules

In Servadra, the rules for a business are authored in its Archon Book, alongside its approved knowledge. They shape what the conversation layer, Meridian, may say, which evidence it may rely on, and when it should stop and bring in a person. The three-circle model gives these rules a clear structure: direct knowledge-base answers, governed AI reasoning, and escalation to staff for matters that need human judgement. Because replies are recorded in an audit trail, a manager can check afterwards whether the rules were followed rather than taking it on trust.

The rules belong to the business, not the software supplier. That is deliberate. Your price policy, your scope and your tone are yours to define and to change. See the how Servadra helps page for how the pieces connect.

Keeping rules alive

A rule set is a living document. Prices change, services are added, regulations and customer expectations move. Set a review date, assign someone to hold it, and keep a simple log of what changed and why. When a decision surprises the team, treat it as a prompt to check whether a rule is missing or out of date rather than as a one-off mistake. Firms that do this find that their rules become shorter, clearer and more trusted over time, which is exactly what people and systems alike need in order to follow them.

A short exercise to try this week

Pick five enquiries you handled recently. For each, write the rule that guided your reply, in one sentence. Where you cannot, you have found an unwritten rule. Where two colleagues would write different sentences, you have found an inconsistency. That small exercise often produces the first useful draft of a rule set.

Questions about business rules

How many rules does a small firm need?

Fewer than most expect. Start with a dozen covering price, scope, response time and escalation, then add only when a real decision keeps going wrong.

Who should approve changes?

Someone with authority over the commercial outcome, usually an owner or director, so that rules do not drift through casual edits.

Can rules be too strict?

Yes. Rules that leave no room for sensible exceptions push people to work around them. Define a clear route for exceptions instead.

Servadra

Related: request a walkthrough · see real-world scenarios · pricing and packages

Related Questions

Can we give different governance rules to pre-sales and after-sales handling?

Yes, and in many organisations that distinction is sensible rather than optional. the governed platform serves different purposes, so the rules that govern them do not need to be identical. A pre-sales exchange may allow more exploratory discussion, while after-sales handling often needs firmer factual boundaries and a more measured tone. The Archon Book allows those differences to be defined clearly, so Servadra behaves like a structured operation rather than a single voice trying to do every job at once.

Can governance rules be shaped around different risk levels in the business?

Yes, governance can reflect differing levels of business risk rather than forcing every enquiry into one uniform handling model. The Archon Book allows an organisation to define where Meridian can operate freely, where the governed platform should remain careful, and where the governed platform must apply tighter service boundaries. That is useful because some parts of a business can tolerate more conversational flexibility, while others require a much firmer standard. Governance makes those risk distinctions operational instead of merely aspirational.

What happens if two internal rules clash with each other?

When rules conflict, Servadra should not be left to improvise a compromise on its own. The Archon Book exists precisely so that those priorities can be defined and resolved in a governed way. That means Meridian are not expected to invent a policy when one rule points in one direction and another points elsewhere. Instead, the conflict should be clarified through the client’s governance structure so that the system follows a deliberate operational decision rather than an accidental one.

Would it be permitted to bypass our rules if it assumes it understands the situation better?

That would be a poor idea, frankly. The service should answer inside the topics, limits, and wording your business has approved, rather than deciding it has suddenly become the managing director. For example, if you approve answers about support hours but not legal advice, it should stick to support and avoid drifting into legal territory. If a customer asks something outside your permitted scope, the safer response is to say the team should handle the detail. You stay in charge of what belongs in customer replies. It is there to follow your rules, not develop a personality and start freelancing.

Can governance rules include how the AI should handle annoyed or aggressive customers?

Yes, governance can and should include that. An annoyed customer is not merely asking a question in a louder tone; the handling approach often needs to change. Through the Archon Book, an organisation can define how Meridian should respond when frustration is detected, when escalation should occur, and how Steward should manage more sensitive service interactions. This ensures the system responds in a controlled and appropriate way rather than treating emotional situations as ordinary informational exchanges.

How stringent are we allowed to make the rules?

You can make the rules as strict as the use case requires. If your business wants a narrow chat that only handles approved service enquiries, that is a perfectly sensible starting point. For example, you may allow simple questions about your services, contact routes, onboarding, and support, while blocking pricing specifics, private details, and anything that needs a human decision. A stricter setup may feel cautious, but cautious is often better than confidently wrong. Your customers still get help where the answer is clear. For anything sensitive or unclear, the conversation can move towards the team. Which subjects would you never want answered automatically?

When a business rule prevents a helpful reply, what approach should Servadra take?

Helpful doesn't mean saying whatever keeps someone happy. When a business rule limits what Servadra can answer, the reply should stay clear, polite, and honest rather than slipping past the rule. For example, if a customer asks for confidential partner commission details, the useful answer isn't to disclose them. It's to explain that commercial details are shared directly with approved partners and that the team can discuss specifics. You still help the person move forward, but you don't sacrifice your own boundaries to sound accommodating. That balance matters more than a sugary reply.

How do we deal with a request that asks the system to violate our terms?

People will try; people are marvellous like that. If someone asks for something outside your approved rules, the answer should stay within your scope rather than helpfully digging a hole. For example, a customer might ask for private staff details, competitor pricing, or an unauthorised commercial promise. Those areas sit outside what Servadra should answer. Instead, it can give a safe response, keep the conversation polite, and point the customer towards an appropriate next step where that fits your setup. You get a calmer front line without letting pushy questions rewrite your rules.