Add validations and review rules

• phone for phone-number inputs.
• email for email addresses.
• integer for whole-number answers, optionally with minimum and maximum values.
• url for website links.
• exact when the user must enter one of a defined set of accepted values.

Use validation where the answer shape matters. Do not over-validate ordinary free text like names or general notes.

If a booking, request, or quote needs confirmation from the business, enable review and define the status pipeline that new submissions should follow.

• Set a default status so new submissions land in the correct queue.
• Add or rename statuses to match the way the team actually works.
• Use status labels that are meaningful to operators, not just generic placeholders.

The Configure tab also controls how the bot summarizes submissions and which update messages should be sent as the status changes.

• Owner notification templates help you receive clearer handoff messages when a new submission arrives.
• Status update templates keep customer-facing updates consistent as the submission moves through the pipeline.
• Summary fields define which answers should stay most visible in the inbox and review UI.
• Notification urgency controls how quickly the owner gets notified.