Know what to build.
Understand why it works.

1. Measure reset volume and confirm the identity-verification policy. Identify an approved identity-provider integration.
2. Create a service-catalogue request with requester identity and account context. Never collect a password in the form.
3. Configure a workflow triggered by the matching request. Add identity checks and the required approval before any reset action.
4. Connect only an approved reset operation; route exceptions to IT. Send a confirmation without credentials.
5. Test successful, rejected and unavailable-provider paths with test accounts. Review logs and repeat-request rates.

Use a test workspace first. Menu names and available actions vary by edition; validate the current product documentation before enabling a workflow.

1. List the applications, access levels, approvers and expiry rules.
2. Add catalogue fields for application, role, business reason and end date.
3. Map the request to an owner and approval path. Keep privileged roles on a separate review path.
4. After approval, create an assigned fulfilment task or call an approved connector. Log the result.
5. Test denied access, duplicate requests and failed provisioning. Add an expiry or review reminder.

Use a test workspace first. Menu names and available actions vary by edition; validate the current product documentation before enabling a workflow.

1. Map HR, IT and manager responsibilities before building the request.
2. Create a catalogue item for role, start date, location and equipment needs.
3. Design parallel tasks for assets, accounts and introductions, with owners and due dates.
4. Require the relevant approvals before creating access. Add a checklist for the new starter.
5. Test a changed start date and a cancelled hire. Confirm rollback ownership and track readiness on day one.

Use a test workspace first. Menu names and available actions vary by edition; validate the current product documentation before enabling a workflow.

1. Review common contact reasons and establish a baseline for first response and reassignment.
2. Define the ticket fields, support groups, priorities and working hours.
3. Create routing automations using clear conditions. Keep a default queue for unmatched tickets.
4. Attach approved response templates and relevant knowledge. Let agents review AI-assisted replies for sensitive cases.
5. Test ambiguous categories, VIP escalations and after-hours requests. Review misroutes before expanding.

Use a test workspace first. Menu names and available actions vary by edition; validate the current product documentation before enabling a workflow.

1. Define the service, team and timeline fields that make a lead useful.
2. Create a contextual greeting for the relevant page. Ask one question at a time and offer a human route.
3. Validate the email address and explain the follow-up purpose before collecting consent.
4. Map fields to the approved CRM integration and assign an owner. Avoid duplicate records using an agreed identifier.
5. Test invalid emails, declined consent and a failed CRM connection. Confirm that the conversation never falsely claims a lead was delivered.

Use a test workspace first. Menu names and available actions vary by edition; validate the current product documentation before enabling a workflow.