Choose what to ask.
Add text fields, contact details, dates and choices. Arrange the questions and mark the ones customers must answer.
Website forms
Turn form submissions into customer records, team conversations and follow-ups. Set the next step before the enquiry arrives.
AFTER SUBMISSION
From your website to your team
A quote request or callback enquiry can reach the right team with the customer details and follow-up already in place.
Aarav Mehta · Contact details saved
Sales inbox
40 starter kits · New enquiry
Check availability and prepare a quoteDue tomorrow
Illustrative example. You choose the routing and actions.
Build the form
Start with a quote request, callback, contact form or newsletter signup. Choose the details your team needs to respond.
Add text fields, contact details, dates and choices. Arrange the questions and mark the ones customers must answer.
Add answers to contact details or custom fields. Keep request-specific information with the submission.
Add your name, logo and brand colour, plus a privacy notice and an expected response time.
Connect an email or phone field to the customer record so WRKZY can identify who’s getting in touch.
Routing and CRM actions
Send requests to the right team, create follow-ups and deals, and keep customer records organised.
Choose a team inbox and default contact owner for incoming enquiries.
Set a task and due date for checking requirements or arranging a callback.
Create a deal in your chosen pipeline and stage, with a title that fits the enquiry.
Apply tags and add the contact to a manual list.
Start an automation for selected forms or every form in your workspace.
Publish and connect
Share a hosted form, add it to your website, or connect the form you already use.
Publish your form and share its link with customers.
Add the form to your website and choose which sites can display it.
Keep your current form. Send submissions to WRKZY through an authenticated server webhook.
Check the form before sharing it. Publish changes when they’re ready, or pause submissions when needed.
Explore integrations ↗The customer’s next step
Confirm the request was received, explain what happens next, and offer a way to continue.
Our team will review the details and get back to you.
Write your confirmation message, add a useful link, or let customers continue on WhatsApp when it’s set up.
Request tracking
See who owns the request, when a response is due, and what still needs attention.
Check the owner and response target. Open the linked conversation to reply.
Find the answers, customer details and related work together, including where the request came from.
Check failed submissions. Authorised owners and admins can resolve customer matches or dismiss spam.
Receiving a submission is only the start. Track whether the customer’s request is finished.
Form results
See how the form performs and what happens to the requests it brings in.
Compare views, starts and submissions, and check the submission rate.
Review requests awaiting a reply, median response time and completed requests.
See deals created from the form and recorded revenue, shown by currency.
FAQ
Website Forms are enabled for all users. Creating, publishing and managing forms or resolving submissions still follows workspace permissions.
Yes. Publish a form configuration in WRKZY and connect your existing form through the authenticated webhook. Send submissions from your server; this is a configured integration, not a one-click connection to every website builder.
Use short or long text, email, phone, number, date, select and checkbox fields. Map answers to contact details or contact custom fields, or keep them only with the submission. A submission must include a mapped email address or phone number.
Yes, when you enable that action and choose a pipeline and stage. You can also configure a follow-up, default contact owner, team inbox, tags and a manual list.
Test submissions are marked separately and do not run the normal downstream customer actions. Preview the form and check a test before publishing the version you want to share.
If the submitted email and phone match different contacts, the submission is held for review. An authorised owner or admin can choose the correct match or dismiss it as spam. Resolving this check is separate from completing the customer’s request.
Built-in checks help catch suspicious submissions and limit excessive requests. Authorised owners and admins can also dismiss submissions under review as spam. These checks reduce abuse; they do not guarantee that every unwanted submission will be blocked.
No. Configure a separate, explicit email marketing consent question if you want to ask for permission. Continuing on WhatsApp is initiated by the customer and does not itself grant marketing permission.
Edit and test a draft, then publish a new version. You can pause a form when you need to stop accepting requests. Public links, embeds and webhooks become available after the first version is published.
Try website forms
Ask for the details your team needs and decide where each request goes.
Start free trial14-day Growth trial · No card required