17GVK

From the website to a service call in the work system.

We built a Hebrew and English website with separate paths for sales enquiries and service requests. The project tested a path for opening service calls in Priority, so an enquiry can continue into the working process instead of ending at a form on the website.

Client
GVK
Type
Client project
  • Bilingual site
  • Enquiry paths
  • Priority
A detail from GVK's Hebrew homepage; figures in the capture are client website content.
A detail from GVK's Hebrew homepage; figures in the capture are client website content.

Context

A Hebrew–English website with separate journeys for commercial enquiries and service requests.

Our work

Visitors can explore services and projects or make a commercial enquiry. Service intake begins with phone identification.

What was built

Bilingual website
Services, projects and enquiry journeys in Hebrew and English.
Service requests
Customer-identification entry into a Priority-connected process.

How the process looks

Before

  • A website enquiry ends at the form

With the system

  1. Website enquiry
  2. Service path
  3. Phone identification
  4. Service call in Priority

The evidence

GVK's public service-intake entry screen, before phone verification.
GVK's public service-intake entry screen, before phone verification.

Scope boundary

This case covers the website and the service-call path tested against Priority. Lead routing, other connections and work agents are not part of this description.

A similar project in your business?

Tell us where the work gets stuck today, and we'll look together at what makes sense to build, connect or improve.