You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User story: As a hub manager or customer advisor, I want to respond to email and contact form queries from the review tab in CXM so that it is easier and quicker to respond to customers.
Acceptance criteria: hub managers and advisors are able to respond to customer queries from review within CXM
All emails out go through “updateus”; any response to any that go out through that (acknowledge, request for further info, etc) should link back automatically (as the email still contains the case reference) so should either attach to the open case or reopen it if its closed….
At least, it SHOULD…. It doesn’t appear to on the new setup yet though! Need to add that onto Github as an issue
The text was updated successfully, but these errors were encountered:
Firstly to reopen a case that's responded to via email Customer Updating a Case does not update or reopen a case and a second request to allow a CIO to respond to a customer from within CXM As a hub manager or customer advisor, I want to respond to email and contact form queries from the review tab in CXM
Can we have them as two separate requests please, as they need to be worked on separately?
Requirement: Respond from review
User story: As a hub manager or customer advisor, I want to respond to email and contact form queries from the review tab in CXM so that it is easier and quicker to respond to customers.
Acceptance criteria: hub managers and advisors are able to respond to customer queries from review within CXM
All emails out go through “updateus”; any response to any that go out through that (acknowledge, request for further info, etc) should link back automatically (as the email still contains the case reference) so should either attach to the open case or reopen it if its closed….
At least, it SHOULD…. It doesn’t appear to on the new setup yet though! Need to add that onto Github as an issue
The text was updated successfully, but these errors were encountered: