Merge pull request #18 from customer-dynamics/documentation-updates

docs: update documentation for clarity

Author: hendrickson-tyler

docs/GETTING-STARTED.md

@@ -104,11 +104,11 @@ Provide the appropriate values in the JSON above, using the following descriptio
 
 The `script` to use for the widget depends on the environment used. For this value, use the URL that corresponds to your environment:
 
-| Environment | Script URL                                                        |
-| ----------- | ----------------------------------------------------------------- |
-| Development | `https://{{Your C3 Vendor ID}}.dev.c2a.link/widget/widget.js`     |
-| Staging     | `https://{{Your C3 Vendor ID}}.staging.c2a.link/widget/widget.js` |
-| Production  | `https://{{Your C3 Vendor ID}}.call2action.link/widget/widget.js` |
+| Environment | Script URL                                                    |
+| ----------- | ------------------------------------------------------------- |
+| Development | `https://agent-apps.staging.c2a.link/web-component/widget.js` |
+| Staging     | `https://agent-apps.staging.c2a.link/web-component/widget.js` |
+| Production  | `https://agent-apps.call2action.link/web-component/widget.js` |
 
 > [!NOTE]
 > Unless otherwise specified for your vendor, use the production script.

docs/features/AGENT_ASSISTED_PAYMENT_IVR.md

@@ -14,10 +14,16 @@ To add these in Webex Control Hub, navigate to the [_Global Variables_ subsectio
 
 The following global variables will need to be defined in your environment:
 
-| Value                  | Type   | Sensitive | Description                                                                                                                |
-| ---------------------- | ------ | --------- | -------------------------------------------------------------------------------------------------------------------------- |
-| `C3Env`                | String | No        | The C3 environment to use in flow (`dev`, `staging`, or `prod`). Unless otherwise specified for your tenant, use **prod**. |
-| `C3PaymentRequestInfo` | String | No        | The information for the C3 payment request, represented as JSON.                                                           |
+| Value                  | Type    | Sensitive | Description                                                                                                                    |
+| ---------------------- | ------- | --------- | ------------------------------------------------------------------------------------------------------------------------------ |
+| `C3Env`                | String  | No        | The C3 environment to use in the flow (`dev`, `staging`, or `prod`). Unless otherwise specified for your tenant, use **prod**. |
+| `C3PaymentRequestInfo` | String  | No        | The information for the C3 payment request, represented as JSON.                                                               |
+| `C3CciAgentId`         | String  | No        | The ID of the Webex agent to transfer back to.                                                                                 |
+| `C3ContactEmail`       | String  | No        | The email address of the contact to use for a receipt.                                                                         |
+| `C3ContactFirstName`   | String  | No        | The first name of the contact.                                                                                                 |
+| `C3ContactLastName`    | String  | No        | The last name of the contact.                                                                                                  |
+| `C3PaymentAmount`      | Decimal | No        | The amount to charge for the payment.                                                                                          |
+| `C3PaymentRequestId`   | String  | No        | The ID of the payment request in C3.                                                                                           |
 
 ### Import Flow
 
@@ -55,6 +61,21 @@ Publish the flow by enabling the _Validation_ switch and then clicking the _Publ
 
 !["An image of Webex Flow Designer, highlighting the validation switch and publish button"](../images/flow-designer-publish.png 'Flow Designer publish')
 
+### Define Variables on Routing Flows
+
+To use C3 during an _outbound_ call, you will need to update the routing flow associated with your Inbound Telephony Channel (otherwise known as an outdial entry point). Likewise, for using C3 with _inbound_ calls, you will need to update the routing flow associated with your Inbound Telephony Channel (otherwise known as an inbound entry point).
+
+For your specific use case, update the flow(s) above to add the following previously defined global variables:
+
+- `C3CciAgentId`
+- `C3ContactEmail`
+- `C3ContactFirstName`
+- `C3ContactLastName`
+- `C3PaymentAmount`
+- `C3PaymentRequestId`
+
+Validate and publish the flow(s).
+
 ### Add a Channel for the IVR
 
 Next, we'll need to add a channel (also known as an entry point) to use for the IVR. This channel will be used to transfer the call to the IVR system.

docs/features/web-link-methods/EMAIL.md

@@ -18,7 +18,7 @@ Before getting started in this section, please ensure the following:
 An app is required to send emails through Webex Connect. To create an app, follow the steps in the [Webex Connect documentation](https://help.webexconnect.io/docs/email-cce).
 
 > [!IMPORTANT]
-> Register this app with the Webex Connect service that you created earlier.
+> Register this app with the Webex Connect service that you created earlier by using the "Register to Webex Engage" button. NOTE: This can only be done once!
 
 ### Create Template