Jimmy Rufo

I don't see this mentioned, but is this supported for classic web widget version of AnswerBot?  I have article suggestions enabled in other channels, and I'd like it in Slack.   I get the below prompt, CC Elizabeth Marshall 

Is there a way we can display to Agents/Admins in looking at a Guide article, if its in draft mode or not?  Today, it seems we have no choice but to wait till someone reports the article being unavailable, and then go into the article settings to check if its in draft mode or published.

Can there be an identifier that can easily show admins/agents if an article is draft vs published, without going into the article config?

+1 here.  This should be added ASAP, for the described use case, and other scenarios.

+1 here.  My organization is trying to turn off domain mapping, and not having the ability to search for this property cripples our ability to properly QA.

Does anyone know the search syntax for organization that have a value in the “Domains” field?  Since wildcard searches don't really work anymore they used to, I'm struggling to find all organizations that are set up for org domain mapping based on a value existing in the “Domains” field.  Please advise.

Hi Team,

I second Nitzan's concern.  We are being forced to verify user email addresses to ensure user mapping is happening to an organization, even though we also use JWT SSO.  We do not require users to set up a password.  Is there a way to disable this requirement via the admin center?

Some feedback on this feature:

1.  The existence of this setting suggests the feature is not very robust, and subject to buggy behavior.  Are there plans to improve stability?

2.  For the errors referenced above and shown to the agent below, can we pleave have an option for this message to  be sent to other admins?  My fear is an agent will set themselves as OOO, not see this message, and leave for a few days.  They may be forget to re-toggle the setting, or simply not see the message.

Hi Barry Neary ,

Thanks for the feedback.  So to summarize, we have a reporting gap for even baseline OCR related assignment (versus manual) till further product updates are made?  I'm open to the “routing queues” method (as opposed to the routing tag method), if it gets us a band-aid report, but are you saying no band-aid is available at this point in either scenario?

All the documentation I reviewed prioritized and highlighted using the routing tag method.

Hi Barry Neary , outside of an upgrade to Explore Enterprise, do you see a way around this for any crude reporting an analyst can create themselves?

We are affected by this exact issue, as some tickets will be assigned via OCR, and some via manual assignment.  Is there a baseline report to show if OCR has at least touched a ticket?

CC Cory Vegel