Customer Handbook
Overview of engagement model, SLAs, communication channels and escalation paths.

What’s new for your team and this portal.
| Phone | DOB | ||
|---|---|---|---|
| No Active staff records found. | |||
| Type | Balance | Used YTD | Units |
|---|---|---|---|
| Select a team member to view data. | |||
All certifications listed here are already completed. This view helps you confirm which staff hold the required certifications for this customer and whether evidence has been verified.
| Employee | Certification | Category | Evidence / verification | Action |
|---|---|---|---|---|
| Indika Herath | Azure Administrator Associate | Cloud & platform | Customer-verified | |
| Sachinthana A. | Power Platform App Maker | Cloud & platform | Evidence on file (internal) | |
| Isuru Solomons | Security Clearance – Level 1 | Security / clearance | Evidence requested |
In a future phase this list can be driven from Dataverse views, with verification state calculated from the latest certification / evidence records for each staff member.
Loaded from OfficeHolidays ICS. Color-coded by holiday type.
Download ICS for the selected year
This view captures the standard working hours for each team member. Customers can quickly see who is available in which time zone when planning meetings and escalations. In a future phase these rows can be populated from BambooHR endpoints.
| Employee | Role | Working pattern | Time zone | Coverage band |
|---|---|---|---|---|
| Indika Herath | Senior Analyst | Mon–Fri 08:00 – 17:00 | Sri Lanka (IST) | Daytime |
| Sachinthana A. | Analyst | Mon–Fri 14:00 – 23:00 | Sri Lanka (IST) | Evening window |
| Isuru Solomons | Support Lead | Rotational weeks (Week A: LK · Week B: UK) | LK / UK | Rotational pattern |
In a future phase these patterns can be driven from Dataverse/BambooHR, with customer-specific working windows and time-zone coverage.
Central place for downloadable assets and key links shared with customers. In future phases these tiles can be driven from SharePoint or Dataverse.
Overview of engagement model, SLAs, communication channels and escalation paths.
How leave and overtime are calculated, approved and reflected in invoices.
Up-to-date certifications, data handling standards and security controls.
Full list of internal and external trainings available for assigned staff.
Later this grid can be driven from Dataverse or SharePoint lists, with permissions filtered per customer.
Quick answers to common questions about the engagement model, leave & shift processes, and day-to-day operations.
In the first week you’ll be introduced to your dedicated team, communication channels (Teams & email) and key artefacts such as the Customer Handbook and escalation matrix.
Related: Customer Handbook, Engagement SLA.
Leave requests can be initiated through the Customer Portal under the Leave tab, or by notifying your account manager. Requests should be raised at least 5 working days in advance where possible.
The Leave & Overtime Policy has more detail on cut-offs and approvals.
Standard working patterns are visible under Shift Times. For after-hours escalations, the on-call rota and contact details are listed in your Customer Handbook and mirrored in Teams.
Response times are driven by the severity level agreed in your SLA. For Sev 1 incidents we respond within 30 minutes and work continuously until service is restored or a stable workaround is in place.
In a future phase these FAQs can be surfaced directly from a Dataverse or SharePoint list, with customer-specific categories and owners.