The work
A Hebrew–English website with separate journeys for commercial enquiries and service requests.
Bilingual website & connected workflows
GVK — Website and service integrations
A Hebrew–English website with separate journeys for commercial enquiries and service requests. Service calls connect to Priority; leads follow a separate path to Fireberry.
Internal portfolio draft — new material is pending publication approval.
- Client
- GVK
- Scope
- Bilingual website & connected workflows
- Focus
- Web / Priority
- Web
- Priority
- Fireberry
- Integrations
FIG. 17 / GVKDRAFT / FOR REVIEW
SYSTEM SIGNALSGVKBilingual website & connected workflowsWebPriority
A Hebrew–English website with separate journeys for commercial enquiries and service requests.
Service to Priority. Leads to Fireberry.Discuss a similar projectCase study
What needed to work better.
Service calls connect to Priority; leads follow a separate path to Fireberry.
How it works
Visitors can explore services and projects or make a commercial enquiry. Service intake begins with phone identification. The integration separates service requests from sales leads, with queueing and duplicate handling for commercial enquiries.
Scope and boundaries
The documentation supports the website and integration implementation, not fresh acceptance of every company workflow. Microsoft 365 connectivity and permissions still need confirmation; SMTP does not establish mailbox or calendar access.
Inside the website
Capabilities
The parts that make the work usable.
Bilingual website
Services, projects and enquiry journeys in Hebrew and English.
Service requests
Customer-identification entry into a Priority-connected process.
CRM lead intake
A Fireberry path kept separate from service requests.