Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hardcoded content #2

Open
martinbon opened this issue Dec 10, 2021 · 1 comment · May be fixed by #9
Open

Hardcoded content #2

martinbon opened this issue Dec 10, 2021 · 1 comment · May be fixed by #9

Comments

@martinbon
Copy link

martinbon commented Dec 10, 2021

Problem:
A lot of the content is hardcoded. How can Tom or any of the CS team start adding SOP's, stats or embed their own stuff in there without having to involve a developer?

V1 suggestion:
Have a link in the menu, that pulls data from an existing on-site wordpress page that CS can modify to their liking.
https://conversionxli.warmpress.com/cs-dashboard/ - example

V5 suggestion:
Have a "Add new sop" button that will create a new SOP in wordpress and will auto-connect the page and the action

@anoblet
Copy link
Collaborator

anoblet commented Dec 14, 2021

The way I envision this is:

  1. Define a set of "actions" (i.e. update customer details, issue refund, update subscription.) These will correlate to buttons/links on the dashboard and sets of SOP.
  2. Outline the steps needed to complete that action.
  3. Set placeholders for where dynamic parts will be ([[ORDER_LINK]], [[CUSTOMER_LINK]], [[REFUND_LINK]])
  4. Make that content available through the REST API (this should be out of the box)
  5. When a CSR clicks a button on the dashboard, it will grab that content and replace those placeholders with the appropriate data for the specific customer, order, etc.

I'm open to other ways of doing it as well.

@anoblet anoblet linked a pull request Dec 28, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants