Scenario & Omnisend
This commit is contained in:
29
ErikaInterview.md
Normal file
29
ErikaInterview.md
Normal file
@ -0,0 +1,29 @@
|
||||
# Interview with Erika
|
||||
|
||||
Tough admin, used enablement and creativity to make it work
|
||||
Created multiple workspaces for the users for that account
|
||||
Client's issue was didn't want to manage multiple accounts, had no bandwidth
|
||||
Used teaching to help the customer
|
||||
|
||||
Needier customers were district contracts
|
||||
Gave her her phone number to client who wanted instant communication
|
||||
Setup regular checkins with these accounts
|
||||
More frequent communication for larger clients
|
||||
Tiered system, small team and each person handled almost 700 accounts
|
||||
Just taking the time explain
|
||||
|
||||
Being an AM was her most enjoyable, creative time
|
||||
Tight knit group
|
||||
Constant communication
|
||||
|
||||
Project Question:
|
||||
Go to learning library, resources first
|
||||
See what's available first
|
||||
Try to connect with client and asking more questions
|
||||
Align with them, is there a temporary fix
|
||||
Check in with peers and see if anyone else has faced this issue before
|
||||
Is there a bridge to solve this temporarily
|
||||
Being honest and aligning with the customer
|
||||
Offer to pushback
|
||||
|
||||
Catalyst for CS with client
|
||||
Reference in New Issue
Block a user