Submit a service request
Send a project, support, change, onboarding, or billing request with enough context for the team to triage it.
Start a requestThis entry is for ePipe Cloud consulting clients. Use it to request a new project, ask for support, track delivery next steps, or ask about billing. Product apps such as the Assets App stay separate from this consulting-client workflow.
The first portal version is intentionally practical: collect the right request details, then let the team set up the right workspace, billing link, or delivery follow-up.
Send a project, support, change, onboarding, or billing request with enough context for the team to triage it.
Start a requestProgress updates are managed through milestones, handoff notes, and a client workspace once the team invites you.
Request workspace accessInvoice access should use approved external billing links or team-issued invitations until a billing provider is chosen.
Ask about billingUntil account access is approved, progress visibility should be team-managed through milestones, notes, workspace invitations, and document handoff.
The team captures the request type, business context, timeline, and preferred next step.
We confirm whether the request is a new project, support item, change request, onboarding need, or billing question.
Active work is tracked with milestones, decision notes, demos, and owner-visible status updates.
Completed work is handed over with notes, documents, links, and follow-up actions.
Post-launch support requests and improvements stay separate from product-app routing.
Tell us what kind of service request this is, how large the business is, and what next step would help. We will route it to the right follow-up instead of treating every client request as a generic enquiry.