Work leads in the inbox

This guide is for anyone signed into the dashboard who handles day-to-day lead triage. You will use Leads (the default list), search, filters, lead detail, and status updates. Developers only need the status section when wiring webhooks that listen for status_changed.

You open a session on the dashboard host.

  1. Open /wckd-forms/dashboard/login (adjust the prefix if your public URL differs).
  2. Enter the email and password for an account that appears under Settings → People & access.
  3. Wait out the throttle window after repeated failures (file-based limiter in wckd-forms/dashboard/security.php).

Screenshot. Show the dashboard login form.

You land on the main table of submissions after a successful login.

  1. Confirm you are on Leads (home / wckd-forms/dashboard/index.php).
  2. Use the column headers or row actions your build exposes to sort or open a row.

You narrow rows by text that exists in stored submission fields.

  1. Locate the search control on the Leads screen.
  2. Enter a fragment of name, email, or other stored text and run the search (or use live search if the UI updates as you type).
  3. Clear the query to restore the full list.

Note. Searchable columns depend on your schema and dashboard helpers; if a field never matches, confirm that column exists on the submissions table.

You slice the same data Performance uses by date, status, and form placement.

  1. Choose a date range preset from the date filter (the button shows the preset name and formatted range, for example Last 30 days with Apr 17 - May 17, 2026), or pick custom start/end dates.
  2. Choose a status value that exists under Settings → Operations lead statuses.
  3. Choose a form scope when the UI offers template or placement label filters.
  4. Combine filters, then open a lead from the reduced list.

Screenshot. Show filters applied with a narrow date range.

You inspect one submission and its metadata.

  1. Activate the row’s view or open action.
  2. Read field values and metadata (timestamps, page_url when captured, IP when shown).

You move a lead through your configured pipeline; valid values come from Operations.

  1. Locate the status control on the lead screen (dropdown, buttons, or inline edit per build).
  2. Pick a status that exists in Settings → Operations lead statuses (invalid values are rejected by update_status.php).
  3. Save or confirm; return to the list and confirm the row shows the new status.

Note. When an HTTPS webhook row has On status change enabled, a successful save can POST JSON to that URL (see Webhooks).

You prove the UI change persisted and optional automations fired.

  1. Reload the lead detail view and confirm the status field still shows the new value.
  2. If you rely on status_changed webhooks, check your receiver logs or queue for a POST whose previous_status matches the old value.
  • Status save fails silently in the UI: the label you picked is not in the configured lead status list; add it under Settings → Operations.
  • Search never finds a field: that field is not indexed or not stored on the submission row your build queries.
  • Webhook fires twice: multiple rows share the same URL and overlapping toggles; audit Settings → Operations → Webhooks.