Workflow Template
Lock change / rekey request Workflow
Manages locksmith lock-change and rekey requests from intake through booking, on-site work, and outcome-based customer communication, with office and locksmith tasks and status tracking end-to-end.
Locksmith teams juggling lock-change and rekey requests often lose track of who's booked, who's on site, and what happened after the job. This workflow takes a request from the public form through urgency-based booking, on-site job completion, and outcome-specific customer emails, with office staff booking visits and locksmiths recording job details. Office admins run the booking side, locksmiths close out the job, and the record's status and timeline show where each request stands at every step.
Business Outcomes
- Faster response to urgent lock-change requests through automatic due-date routing
- Fewer missed bookings with dedicated office tasks for urgent and standard visits
- Clearer customer communication with automatic acknowledgement, booking and outcome emails
- Better visibility into job outcomes with separate handling for completed, further-work and unable-to-complete jobs
- More consistent feedback collection with an automatic post-job feedback request
Workflow Steps
Steps
- 1Create Lock Request Recordcreate record
Registers the submitted request as a lock request record.
- 2Set Status to New Requestupdate record
Sets the record status to New Request.
- 3Send Acknowledgement Emailsend email
Emails the customer an acknowledgement with their reference number.
- 4Route on Urgency
Routes the booking task due date based on urgency.
urgency: "Urgent"→Office: Book Urgent Visiturgency: "Standard"→Office: Book Standard VisitDefault→Office: Book Standard Visit - 5Office: Book Urgent Visitcreate task
Office schedules an urgent visit, recording the visit date and assigned locksmith, due in 1 day.
- 6Office: Book Standard Visitcreate task
Office schedules a standard visit, recording the visit date and assigned locksmith, due in 3 days.
- 7Save Booking Detailsupdate record
Saves the visit date and assigned locksmith to the record and sets status to Booked.
- 8Email Visit Date to Customersend email
Emails the customer confirming the scheduled visit date.
- 9Locksmith: Complete Jobcreate task
Locksmith records the work completed, key system, keys handed over, photos and outcome, with no due date.
- 10Save Job Detailsupdate record
Saves the job details captured by the locksmith to the record.
- 11Route on Job Outcome
Routes handling based on whether the job was completed, needs further work, or could not be completed.
job_outcome: "Completed"→Set Status to Completedjob_outcome: "Further work needed"→Set Status to Further Work Requiredjob_outcome: "Unable to complete"→Set Status to Unable to CompleteDefault→Set Status to Completed - 12Set Status to Completedupdate record
Sets the record status to Completed.
- 13Email Work Summary to Customersend email
Emails the customer a summary of the work done.
- 14Wait 2 Days Before Feedback Request
Waits two days before requesting feedback from the customer.
- 15Request Customer Feedbackrequest external input
Sends the customer a feedback form with a 1-5 rating and comments.
- 16Set Status to Further Work Requiredupdate record
Sets the record status to Further Work Required.
- 17Email Findings and Further Work Neededsend email
Emails the customer the findings and the work still needed.
- 18Office: Prepare Quotecreate task
Creates a fire-and-forget task for the office to prepare a quote for the further work, due in 2 days.
- 19Set Status to Unable to Completeupdate record
Sets the record status to Unable to Complete.
- 20Email Findings to Customersend email
Emails the customer the findings explaining why the job could not be completed.
Fields
- Full Name*
- Email*
- Mobile Number*
- Site Address*
- Job*
- Reason*
- +16 more fields
Forms
Lock Change / Rekey Request
12 fields
Data Views
Lock Requests Overview
customer_name, site_address, job_type, urgency +3 more
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
How do I set up this workflow for my locksmith business?
Publish the template to your workspace and it's ready to run immediately, no installation or development needed. You'll want to add your office and locksmith team members so tasks like booking visits and completing jobs can be assigned to them. The public request form is live as soon as you publish, so customers can start submitting lock-change and rekey requests right away.
How does the workflow decide whether a visit is urgent or standard?
The customer selects an urgency level on the request form, and the workflow routes the booking task's due date accordingly. Urgent requests create an office task due in 1 day, standard requests create one due in 3 days, and any other value falls through to a default path. This keeps urgent jobs visibly time-boxed for the office team without anyone having to check manually.
Who is responsible for booking the visit?
Office team members handle booking, either through the urgent or standard visit task depending on how the request was routed. The workflow waits for whichever booking task applies, and the visit date and assigned locksmith they enter get saved to the record and set the status to Booked. The customer then automatically receives an email confirming the visit date.
What happens after the locksmith finishes the job on site?
The locksmith completes a task recording what was done, the key system used, keys handed over, job photos and the outcome. The workflow waits for this task, saves those details to the record, and then routes the process based on the outcome the locksmith selected. This means every job's result is captured on the record before any customer communication goes out.
What's the difference between the three job outcomes?
If the outcome is Completed, the record status is set to Completed and the customer gets a work summary email, followed by a feedback request two days later. If it's Further Work Needed, the status becomes Further Work Required, the customer is emailed the findings, and a fire-and-forget task is created for the office to prepare a quote. If it's Unable to Complete, the status is set accordingly and the customer receives an email explaining the findings.
Can I change the due dates or task assignments?
Yes. You can describe the change you want in plain English, or open the workflow editor and adjust the steps directly, including due dates on the booking or quote tasks. Earlier versions of the workflow are kept, so you can review what changed over time.
Do customers need to create an account to submit a request or respond to forms?
No. Customers submit their initial request through the public request form, and any follow-up forms, like the feedback request, are emailed directly to them. They complete everything without needing to log in or set up an account.
Where do I see the status of every lock-change request?
Each submitted request becomes a record with its own reference number, status, and timeline showing what's happened so far. Table views and dashboards group these records by status, such as New Request, Booked, Completed, Further Work Required, or Unable to Complete, so office staff can see where things stand at a glance.
What happens to the Quote Notes the office enters for further work?
The Prepare Quote task is fire-and-forget, meaning the workflow doesn't wait for it to finish. Because of that, the Quote Notes entered on that task stay with the task itself and appear in the record's task list, rather than being saved directly onto the main record.
How is customer feedback collected and where does it go?
Two days after the work summary email is sent, the workflow sends the customer a feedback form asking for an overall satisfaction rating and any comments. Since this form is completed by the customer directly, their answers are saved onto the record for your team to review.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
