Skip to main content

Webforms & Inbound Email

ServCraft can capture service requests from two external sources — an embeddable webform on the business's website, and inbound emails forwarded to a ServCraft address. Both automatically create Queries, giving the team a single inbox for all incoming requests regardless of how they arrived.


Webforms​

What Is a Webform?​

A webform is an embeddable form that a service business places on their own website. When a prospect or customer fills it in and submits, a Query is automatically created in ServCraft — no manual data entry required.

The business controls what fields appear on the form, what type of query is created, and who it gets assigned to.

Webform Types​

When setting up a webform, the business chooses a type:

TypeUse case
Contact UsGeneral enquiry from the website
Log Service RequestCustomer requesting a service call
Register WarrantyCustomer registering a purchased product
Item BookingCustomer booking a service slot

The type categorises the query and can be used to filter and route queries differently.

Setting Up a Webform​

Web forms live under Settings, in the Templates group, under Web Forms. Click Add Web Form to start a new one.

Creating a web form happens in two steps. The create screen asks for the basic settings below. When you click Create, ServCraft saves the form, switches it on, and opens its edit screen, where the embed code, the field labels and the Active switch appear.

Setting on the screenWhat it does
Name (required)Internal name for this form
Title (optional)Heading displayed to the visitor on the form
Type (required)Contact Us, Log Service Request, Register Warranty or Item Booking. The type decides which fields the form has and cannot be changed after the form is created.
Your website domain (required)The website the form will be embedded on, for example https://mywebsite.com. It must start with http:// or https:// and be the domain only, with no page path after it. The form only works on this domain.
Query Type (required)Which query type is created when the form is submitted
Query Status (required)Starting status for new queries from this form. The list shows the statuses of the chosen query type.
Follow Up Time in Minutes (required)How many minutes after submission the query's follow-up date is set
Assign Employee (optional)The employee new queries from this form are assigned to
ColumnsLays the form out in 1 or 2 columns. It can be changed later on the edit screen.
Edit Form StyleOpens a Background Colour and a Text Colour picker for the form, to match the business's branding

On the edit screen the same settings appear under Web Form Details, with Save, Preview and Cancel buttons at the top. Preview opens the form in a new browser tab so you can check it before it goes on the website.

The Form's Fields​

The fields on a web form are fixed by its type. You cannot add or remove fields, but you can rename them and choose which of them are required.

TypeFields
Contact UsFirst Name, Last Name, Phone Number, Email Address, Comment
Log Service RequestFirst Name, Last Name, Inventory (a dropdown of the business's items), Serial Number, Date of Purchase, Phone Number, Email Address, Attachment
Register WarrantyFirst Name, Last Name, Inventory, Serial Number, Date of Purchase, Phone Number, Email Address, Attachment
Item BookingFirst Name, Last Name, Phone Number, Email Address, Customer Name, Inventory, Comment

After the form is created, the Edit Form Items section of the edit screen lists each field with:

  • Label for the field, the text the visitor sees next to it
  • a Required tick box
  • Validation message for the field, the error shown when a required field is left empty (only shown while Required is ticked)

Some fields are always required and their Required box cannot be unticked: First Name and Last Name on every type, Comment on Contact Us and Item Booking, and Inventory on Register Warranty and Item Booking. On a Contact Us form, Phone Number and Email Address are the fields that can be switched between required and optional. Phone Number and Attachment start out optional; every other field starts out required.

Comment boxes allow up to 400 characters. The Attachment field accepts a document or image upload; the limit is checked on the encoded upload, so files over roughly 3MB are rejected as too large.

The Active switch at the bottom of the edit screen turns the form on and off. A form that is switched off stops loading and accepting submissions on the website. Click Save after changing anything on the edit screen.

Customising the Look and Feel​

The webform can be styled to match the business's website in two ways:

1. Background and Text Colour (in ServCraft)​

When creating or editing the webform, the Edit Form Style button lets you pick a background colour and text colour using a colour picker. These apply to the entire form and are the quickest way to match basic brand colours.

2. CSS Injection (on the website)​

For full styling control, add a meta tag to the <head> of the page where the form is embedded:

<meta name="servcraft-css-override" content="YOUR CSS HERE" />

The embed script reads this tag and injects the CSS directly into the form. The CSS is sanitised before use.

Example — remove rounded corners from inputs:

<meta name="servcraft-css-override" content=".form-control { border-radius: 0px; }" />

Example — multiple rules:

<meta name="servcraft-css-override" content="
body { font-family: 'Inter', sans-serif; }
.form-control { border: 1px solid #333; border-radius: 4px; }
.form-title { color: #003ED0; font-size: 1.4rem; }
.btn-light { background: #003ED0; color: white; border: none; }
" />

Key CSS selectors to target:

SelectorWhat it styles
bodyForm background and base text colour
#servCraft_FormContainerThe outer form wrapper — controls padding and width
.form-titleThe form heading (bold, 1.2rem by default)
.webform-fieldEach field row (label + input)
.webform-field .form-labelField labels
.webform-field .form-controlText inputs, dropdowns, date pickers, textareas
.btn-lightThe Submit button
.errorValidation error messages (red by default)

The meta tag must be on the page that hosts the Script + Div embed. Behind the scenes the script renders the form in a frame it manages, and it passes your CSS through to the form automatically.


Getting the Embed Code​

After creating the webform, open it from Settings → Templates → Web Forms. The top of the edit screen shows three snippets, each with a Copy button:

Script + Div:

<script type="text/javascript" src="https://api.servcraft.co.za/Scripts/embed-form.js" async defer></script>
<div id="servCraft_Container" data-key="[YOUR-KEY]"></div>

The script goes in the page's <head>; the div goes in the <body> where the form should appear. The script then renders the form on the page (inside a frame it manages — no separate iFrame code is needed or provided).

The third snippet is optional: an example servcraft-css-override meta tag for the page's <head>, used to apply custom CSS so the form matches the website (see Customising the Look and Feel above).

What Happens When a Form Is Submitted​

  1. The visitor fills in the form and clicks submit
  2. ReCAPTCHA validates the submission (prevents spam)
  3. ServCraft creates a Query with:
    • Source = Webform
    • Flagged as Draft (so staff review it before progressing)
    • Status = the configured default query status
    • Type = the configured query type
    • Assigned to = the configured employee (if set)
    • Follow-up date = submission time + configured timespan (in minutes)
    • Description = a summary of the submitted fields
    • All form data stored against the query
  4. If the submitted email address matches a known customer contact in ServCraft, the query is automatically linked to that customer — no manual work needed
  5. If the email doesn't match, the query is created without a customer link and staff assign it manually
  6. Any file attachments are saved to the query automatically
  7. Queries created this way go through the standard Query trigger system, so a trigger can send a notification to the assigned employee or team

Customer Matching​

The webform compares the email address field (if included) against existing customer contacts in ServCraft. If a match is found, the query is linked to that customer and contact automatically. (For Item Booking forms, matching is done on the customer name instead, and the matched customer's store is used; other form types use the default store.)

If no match is found, the query still gets created — staff see it unassigned and link it to a customer manually.

Tip: Including an email field on the webform enables automatic customer matching. Without it, all submissions require manual customer assignment.


Inbound Email → Queries​

What Is Inbound Email?​

Inbound email allows a service business to forward customer emails to a ServCraft-monitored address. When an email arrives, ServCraft automatically parses it and creates a Query — giving the business a single place to manage all incoming requests, whether they came in via the website or email.

How It Works​

  1. ServCraft staff set up an inbound address for the business (see Configuration below)
  2. The business creates a forwarding rule on their support inbox (e.g., support@theirbusiness.co.za) that forwards every email to that inbound address
  3. When a customer emails the support inbox, the forwarded copy reaches ServCraft's email service, which works out which business it belongs to from the inbound address
  4. ServCraft parses the email: the subject becomes the query's Reference, the body becomes the description, and attachments are saved
  5. A Query is created with:
    • Source = Email
    • Flagged as Draft (requires staff review before progressing)
    • Reference = the email subject
    • Description = a "From:" line with the sender's address, followed by the email body text
    • Follow-up date = 1 hour from arrival (default)
    • Attachments = any files the customer attached
  6. If the sender's email address matches a known customer contact, the query is automatically linked to that customer
  7. If not matched, the query is created without a customer link and staff assign it manually

In the query list these queries show Inbound Email as the creator.

Query Status on Arrival​

Inbound email queries are created as Draft. They appear in the query list and staff must:

  1. Review the query
  2. Assign it to a customer (if not auto-matched)
  3. Set the query type and status
  4. Assign to an employee
  5. Progress it through the workflow

This manual review step is intentional — it ensures the query is correctly categorised before the customer is contacted.

Automatic Customer Matching​

ServCraft compares the sender's From email address against all customer contacts. If a match is found:

  • The query is linked to that customer automatically
  • The correct store is assigned (for multi-store businesses)

Automatic matching is on by default but can be switched off per business (a configuration option — ask support).

If the sender email doesn't match any known contact, the query is still created — it's flagged as unassigned and staff link it manually.

Practical tip: Encourage customers to email from the address on their contact record. This maximises auto-matching and reduces manual work.

Configuration​

Settings → Queries — query types, statuses, and custom fields for inbound queries can be configured here.

Verifying the forwarding rule​

Most email providers send a verification email to the forwarding address before they start forwarding. That email goes to the inbound address, so it never reaches the business's normal inbox. It arrives in ServCraft as a new draft query like any other inbound email, with the provider's message, including the verification link, in the description. To complete the setup:

  1. Go to Queries and open the new query created by the verification email.
  2. Copy the verification link from the description.
  3. Paste it into a browser to confirm the forwarding.

Once the provider has verified the forwarding, every forwarded email lands in ServCraft as a query.

Getting Notified When an Email Creates a Query​

Yes, staff can be notified every time an inbound email creates a query. This is done with a trigger that uses the Email to Query Create rule on the Query module. The rule fires once, at the moment a new query is created from an inbound email. It does not fire for queries created by hand, from a webform or through the API, and it does not fire again when the query is later edited.

To set it up:

  1. Go to Settings, and under Templates open Triggers, then create a new trigger.
  2. Under Trigger Settings, set Trigger Module to Query.
  3. Enter a Trigger Name, for example "New inbound email query". The name is required.
  4. Set Trigger Rule to Email to Query Create. The Rule Settings panel shows "No settings required", because this rule has no conditions to fill in.
  5. Under Trigger Actions, set Action Type to Communication. It is the only action type offered.
  6. Choose the Notification Type. To alert the office, pick Employee and choose the person in Recipient, or pick Employee All to notify every employee.
  7. Tick Send Email, Send SMS or both (at least one is required) and choose a Message Template. The template is required, and a new one can be added from the same dropdown.
  8. Use Add Another Action if more than one notification is needed, then click Create.

Avoid Assigned Employees for this rule. An inbound email query has no employee assigned when it is created, so that option reaches nobody. The customer contact options send the notification to the customer, and only when the sender was matched to a known contact.


Webform vs Inbound Email — Quick Comparison​

WebformInbound Email
How it arrivesCustomer fills in form on websiteCustomer sends an email
Arrives as Draft?YesYes
Query status on arrivalConfigured default statusNot set — staff assign manually
Customer matchingVia email field on formVia sender email address
File attachmentsYes (roughly 3MB max — the 4MB limit is applied to the base64-encoded content)Yes
Query type assignedConfigured on the webformNot set — staff assign manually
Assigned employeeConfigured on the webformNot set — staff assign manually
Trigger supportYesYes (Email to Query Create trigger)
Requires staff review?Less — query is pre-configuredMore — arrives as Draft

Common Scenarios​

"A website submission came in but we can't find the query"​

  1. Go to Queries → Query List
  2. Turn on the Draft filter — webform queries arrive flagged as draft
  3. Also check if the query was auto-assigned to a specific employee — filter by Employee
  4. If not there at all: check the webform configuration — is Your website domain set correctly and is the form Active? A domain mismatch or a switched-off form blocks submissions.

"Queries from inbound email are all unassigned"​

This is expected if no customer contact has that email address on file. Have staff assign the customer manually, and consider adding the email to the contact record so future emails auto-match.

"We want different team members to handle website vs email queries"​

Configure the webform with a specific Assign Employee. For email queries, set up an Email to Query Create trigger that notifies the person who handles email queries. Triggers only send notifications; they cannot assign the query, so that person assigns it after reviewing it.

"The webform isn't appearing on our website"​

  1. Confirm the embed code is placed correctly in the page HTML
  2. Check the Your website domain setting on the webform matches the exact domain (including https://) — a mismatch will prevent the form from loading
  3. Check that the form's Active switch is on; a switched-off form does not load
  4. Check whether the page is using a content security policy that blocks iFrames or external scripts

"A customer submitted the webform twice with the same issue"​

Two queries will have been created. Review both, close the duplicate, and work the original. Consider adding a note on the duplicate explaining it was merged.