Turn webinar questions into Salesforce tasks for owners

**Objective:** Route the questions asked in the GoTo Webinar webinar `{webinar}` to the Salesforce owner of each asker's contact or lead as a follow-up task. Route only unanswered questions unless `{unanswered-only}` is no (default yes).

**Step 1: Find the webinar**

Call `goto-webinar-get-webinar` (GoTo Webinar) with `webinar-name.contains` set to `{webinar}`. If `{webinar}` is all digits, filter by `webinar-key` instead. If more than one webinar matches, list each one's webinar-name, date and webinar-key and stop so the user can choose. If none match, say so and stop. Keep the `webinar-key`, `webinar-name` and `date`.

**Step 2: Read the questions**

Call `goto-webinar-get-question` (GoTo Webinar) with `webinar-key`. A question is unanswered when its `answer` is blank. Unless `{unanswered-only}` is no, keep only unanswered questions. Group the questions by `askers-email`, and put questions with a blank askers-email in a separate "anonymous" list.

**Step 3: Find each asker in Salesforce**

Match each email address to Salesforce in this order, and stop at the first hit:
1. `salesforce-get-contact` (Salesforce) with `email` set to the address. A hit is a contact: keep `contact-id`, `name`, `account-name`, `account-id` and `owner`.
2. `salesforce-get-lead` (Salesforce) with `email` set to the address. A hit is a lead: keep `lead-id`, `name`, `company`, `status`, `converted` and `owner`. Ignore leads where `converted` is true when a contact also matched.
3. No hit on either: the person is unknown to Salesforce.

Compare addresses case-insensitively and trimmed. Never match on name alone. If one address matches more than one contact, or more than one unconverted lead, mark the person "ambiguous" and list every match rather than picking one.

**Step 4: Find each owner's user id**

For each distinct owner from Step 3, call `salesforce-get-user` (Salesforce) with `name` set to the owner and `active` true. Keep the `user-id`. If no active user matches, or more than one does, leave that owner unresolved and do not guess.

**Step 5: Confirm**

Show a table: asker email, contact or lead, record name, owner, number of questions, the questions themselves (shortened to 150 characters each). STOP and ask the user to confirm which rows get a task. Create nothing until they do.

**Step 6: Create the tasks**

After confirmation, call `salesforce-add-task` (Salesforce) once per confirmed asker with:
- `who-id`: the contact-id or lead-id
- `assigned-to-id`: the owner's user-id (leave it out if unresolved; Salesforce then assigns the task to the caller)
- `subject`: "Webinar question follow-up: " followed by the webinar-name
- `priority`: High when any of the asker's questions is unanswered, otherwise Normal
- `comments`: every question with its time-asked and any answer given
If a call fails, record the error and continue.

**Step 7: Report**

Created tasks with ids and owners, then unknown askers (email and questions) and anonymous questions, since those need a human to pick up.

**Rules & Guidelines:**

* Tools starting goto-webinar- are on the GoTo Webinar server; tools starting salesforce- are on the Salesforce server. Both must be connected.
* The only write this prompt may make is `salesforce-add-task`, after the user confirms in Step 5.
* Do NOT call `salesforce-add-lead`, `salesforce-add-contact`, `salesforce-update-task`, `salesforce-update-contact` or `salesforce-update-lead`. Do NOT call `goto-webinar-add-registrant` or `goto-webinar-delete-registrant`.
* One task per asker, not per question.

**Validation:**

* If the webinar has no questions, or none unanswered when only unanswered are wanted, say so and stop.
* Do not create a lead for an unknown asker; that is a separate job.