01
Be clear about what is included
The expert in a standard Zemark bundle is the AI agent. Human management by Pobuca is a separate service with an additional charge.
That distinction matters. A client employee approving an email, a service representative receiving an escalation and a Pobuca specialist managing the agent are three different roles.
The service proposal should state which Pobuca activities are included, what remains with your team and which technical or commercial decisions require a separate process.
For Zemark for CRM, optional human management can support campaign strategy, review and optimisation within a separate service scope. It is distinct from the AI personal marketer, standard onboarding, technical support and Reach fieldwork.
02
Establish the operating priorities
Start with the Zemark offering in use and the work it supports: field sales, CRM, loyalty/engagement or service. Identify the outcomes, sources, instructions and systems relevant to that process.
The managed-service scope can then define how the team reviews activity, handles operational questions and coordinates changes. A CRM assistant and a customer-service agent should not receive an identical management checklist simply because they share a name.
03
Keep knowledge and instructions useful
An agent relies on the material and rules it is allowed to use. Product information, communication guidance and operating procedures can change.
The agreed service can help coordinate approved updates and review where instructions are unclear. Your business remains responsible for supplying or approving authoritative facts and material commercial decisions.
Sensitive customer information and one-off exceptions should not become general knowledge without the appropriate review. The point is maintained quality, not automatic publication of everything the agent encounters.
04
Review the work and its exceptions
Examine what Zemark completed, what required a person and which issues repeat. The available evidence depends on the configured workflow and reporting.
For CRM, a review may concern record quality and ambiguous updates. For Loyalty, it may concern campaign preparation and participation. For Service, it may concern knowledge gaps and handoffs. For Sales, it may concern useful preparation and follow-through.
The review should produce specific actions and owners rather than a general assurance that the agent is “learning.”
05
Coordinate the right improvement
Some changes concern approved wording or operating instructions. Others require a new integration, different permissions or additional software work.
Customer Success can help identify and coordinate the distinction. Technical development and new product entitlements are not silently included in the management service.
Where a change affects external communication or a business action, the relevant review and testing should happen before it is enabled.
06
Keep business approval practical
Agree which decisions your team reviews and how it receives the necessary information. An approval should show the proposed action and its context.
The service does not transfer unlimited commercial authority to Pobuca or the agent. Prices, programme changes, customer commitments and other consequential decisions follow the agreed responsibilities.
A useful management model reduces confusion about who decides, who acts and who checks the outcome.
07
See what the agent delivers — and improve what happens next
Your Customer Success team reviews the work Zemark completes, the exceptions that need attention and the effort released for your business. Reporting makes the operating picture visible; a structured review turns it into priorities.
The service can cover knowledge improvements, clearer instructions, campaign or service-process refinements and coordination with the technical team. Agreed actions are tracked through to the next review so recurring issues do not remain in the report indefinitely.
The frequency of reporting and meetings follows your managed-service agreement. This is the separately charged human service around Zemark, not an implied consulting entitlement in every software-and-agent subscription.
08
An illustrative service review
The team notices that the agent repeatedly asks for clarification on the same type of request. Customer Success reviews the relevant evidence and identifies whether the cause is missing source information, unclear instructions or a technical limitation.
The client supplies or approves the required facts. An operational update is made within scope, or a technical requirement is raised. The next review checks whether the issue is reduced without creating new errors.
This is the kind of continuity a human-managed service can add around an AI agent.
Is this required to use Zemark?
It is an additional service option, not the definition of the standard software-and-AI-expert bundle.
Does Pobuca approve every action instead of us?
The responsibility model determines approvals. Important business decisions remain with the appropriate authorised person.
Are new integrations included?
Only when explicitly included in the service or project agreement. New engineering work needs its own scope.
Is technical incident support the same service?
No. Technical support and human operational management should have clearly distinguished arrangements.
Choose the human support that helps your AI expert work well for your business. Book a discovery meeting.