TAHAI Web Services logoTAHAI Web Services
MSP + MSSP operations suite

Start with Operational Intelligence. Use TAHAI PSA for service workflow and TAHAI IT Docs for documentation and client records.

Implementation path

Roll out Operational Intelligence with PSA and IT Docs underneath.

Start with the flagship operating view, then map the service workflows, documentation foundation, user roles, evidence boundaries, and client-facing visibility needed to make the rollout clean.

Rollout sequence

A cleaner path from first review to accountable operations.

The goal is not to turn everything on at once. The goal is to put the operating model, service workflows, records, visibility, and trust pages in the right order.

1

Confirm the operating goal

Decide whether the first outcome is owner visibility, service floor visibility, project rescue, finance leakage, client QBR, security posture, or documentation cleanup.

2

Map PSA workflows

Identify the service operations, ticket context, approvals, dispatch pressure, project status, and follow-through that need to be visible.

3

Organize IT Docs records

Clean up client records, procedures, handoffs, projects, and approved client-facing material before relying on them in a higher-level board.

4

Confirm roles and boundaries

Separate Owner, Staff, Client View, product admin, evaluator, and reviewer needs. Keep internal operations away from read-only client visibility.

5

Review trust and data-handling pages

Use the public trust, security, data handling, legal, status, and support pages before requesting custom procurement materials.

6

Open the right live product

Use OI for the operations board, PSA for service workflows, and IT Docs for documentation and records foundation.

Role clarity

Client View stays separate from staff work.

A clean implementation keeps approved client-facing visibility distinct from internal operational records, billing context, secrets, automation, and staff workflows.

  • Owner and Staff are internal operational roles.
  • Client View is read-only and limited to approved client-facing material.
  • OI and PSA workflow access should be assigned according to the work a person actually performs.
Procurement path

Give reviewers a stable review path.

The public site keeps procurement, trust, legal, security, and data-handling materials easy to find before a deeper review.

FAQ

Implementation questions

Practical answers for the updated product lineup.

What is the safest starting point?

Start with the operating question: owner visibility, service pressure, projects, finance leakage, client QBR, security posture, or documentation cleanup.

When do we use OI?

Use Operational Intelligence when the work needs an operations view across PSA, IT Docs, projects, client health, finance, evidence, and trust posture.

When do we use PSA?

Use PSA for service operations, tickets, approvals, dispatch pressure, and service workflow follow-through.

When do we use IT Docs?

Use IT Docs for documentation, procedures, client records, approved client-facing material, and operational memory.

Open the live implementation path.

Start from OI, then map PSA and IT Docs underneath the operating view.

Looking for the MSP or MSSP product?

Start with Operational Intelligence, use PSA for service workflows, and keep operational records in IT Docs.