Frequently Asked Questions


Potentially. The required languages need suitable source content, testing and an escalation plan.

Yes. Parties, territories, shared opportunities and responsibilities can be modelled explicitly.

Only within applicable channel rules and your approved consent and messaging practices. Outbound campaigns need their own operating scope.

That needs an explicitly scoped workflow or agent capability with separate permissions and testing.

Yes, subject to source quality, rights, format, access and an agreed update process.

We check available interfaces, permissions and failure behaviour before confirming integration scope.

Yes. Permissions can be designed by role, team or relationship type and checked with representative users.

Yes. We can review feasibility, identify dependencies and help shape the technical scope. The extent of pre-sales and discovery work is agreed in advance.

Yes, when they remain fit for purpose. Existing systems can be integrated, rescued or extended before replacement is considered.

Yes, but only when the current platform or content estate prevents the accepted outcome. The report should also identify when focused repair is sufficient.