Workflow: New User (New Contact) for Current Customer

Workflow: New User (New Contact) for Current Customer

Any time a new user is onboarded, whether the customer explicitly says so or not, you (the person responsible for the ticket at any given time) must perform the following action to ensure they are properly onboarded in our systems and in the customer's systems. Whether the customer says, "We are onboarding a new user," or merely, "I need an email address set up," you should be thinking about the bigger implications of this. 

In AT ticket, choose category Administrative Change/Request. 
Choose ticket template "Add New Contact/User for  RMM customer."
The notification section of this template causes the ticket contact to receive an email with a link to our new user form.
When the customer ticket contact completes the form, the data is automatically sent to the form as a ticket note via the following: 

  1. Form is received by Autotask via form designer
  2. Form is configured to send the form data to the email address  newcustcontact@geekgirlsit.com
  3. Power Automate trigger sends the data to the ticket as a ticket note using the AT mailbox forms.NYGG.LOCAL@email.autotask.net . The "sender" is info@nygeekgirls.com
  4. The same Power Automate flow checks whether the form submitter wants the user added to the Newsletter group in MailerLite. If so, it adds the customer to the group. 

Alert
The integration between PA and Mailerlite requires a PA Premium license, which is attached to Roberta's mailbox. 
 
The contact info is automatically added to Autotask. (This functionality uses Autotask's AutoForms Designer feature.)

Admin receives notification of the info via AutoForms. It goes to the office@ mailbox.  

The following items are included in the ticket checklist, and will be completed and checked off by the Office Admin:

  1. Admin adds info to Hudu including whether user is auth contact, to which DLs user belongs, etc. 
  2. Admin follows up if form indicates customer wants a computer quote.


From this point on, the checklist can be followed. 


Notes
If the ticket number doesn't exist, Autotask will send a notification to roberta's email address


    • Related Articles

    • RMM Workstation Setups, Swaps, and Removals: Workflow

      Adding an RMM Workstation or Swapping Users on an Existing RMM workstation. Start with ticket category: Curr MSA, add/del device/service Use ticket template 072: [Current Customer] RMM New Device Setup Follow instructions in the ticket description to ...
    • New Authorization Contact for Current Customer - Workflow

      In AT ticket, choose category Administrative Changes. Choose ticket template "[Current Customer] Add or Replace Authorization Contact for Current RMM Customer." The notification section of this template causes the ticket contact to receive an email ...
    • Remove Contact (User) for RMM Customer

      Use ticket category: Administrative Change/Request. Confirm the ticket contact field is populated Choose ticket template "[Current Customer] Remove Contact/User for Current RMM Customer". Add either the generic or the customer-specific checklist for ...
    • New Prospect and Client Intake Instructions (New Customer)

      This procedure applies to inactive customers in AT as well as to customers that have not opened a ticket or been billed by us in at least one year. They are to be treated as new customers. The only difference is that instead of creating the account ...
    • Add New Contact to Existing Customer (Including Email Setup)

      Use one ticket per new contact. Do not put two contacts on the same ticket. It's not recommended to clone this ticket unless you're very confident that the "new user form" email will get sent correctly to the authorization contact. It's safer to ...