Customer self-service

Let customers request service directly from your website.

An embedded Sepolo service form can give customers a better way to report issues, attach images and describe the affected asset before the dispatcher starts planning.

Website embed
Structured intake
Dispatcher approval
Photo documentation
Let customers request service directly from your website.

A better first request than a phone note.

The service request can collect customer, contact, site, asset, issue description, images and preferred time window. The dispatcher receives structured input and can approve, enrich and plan the request in Sepolo.

Website embed
Structured intake
Dispatcher approval
Photo documentation

Field service platform

A concrete service workflow, not just a product page.

01

Embed on common website platforms

The module can be designed for Squarespace, WordPress, Wix and similar sites using a controlled iframe or script embed.

SquarespaceWordPressWixDomain protection
02

Capture the details dispatch needs

Customers can describe the problem, choose location or asset, upload photos and add contact details before the request reaches the service desk.

Contact dataLocationAssetImages

What you get

Answers to the questions buyers actually have.

03

Protect the service queue

Requests should be validated before they become service visits. Captcha, rate limiting, file limits and allowed domains keep the intake controlled.

CaptchaRate limitingFile limitsAllowed domains
04

Convert request to service visit

The dispatcher can approve the request, add SLA and agreement context, assign technician and move the job into the normal Sepolo flow.

ApprovalSLA contextTechnician planningService report

Next step

A 30-minute walkthrough with concrete answers.

We start from your service flow, assets, technicians, ERP and the places where time is lost today.

Discuss self-service
Let customers request service directly from your website. | Sepolo