Your customers speak.
Your agent gets to work.

Keep working in your chat or terminal. Give your agent access to UserGist, find the story in customer feedback, and prepare your next update right there.

Start free Explore the workflows

Agentic workflows are rolling out to enabled workspaces.

The same task, in chat or in your terminal.

ChatGPTChat

Use UserGist to find what’s confusing people about offline maps.

Reading customer feedback in UserGist…

trailsideTerminal

Claude Code~/projects/trailside

Use UserGist to find what’s confusing people about offline maps.

● UserGist search

Illustrative conversations. No live connection or workspace changes.

An answer with the customer still in it.

Ask what people are struggling with. Your agent can read feedback, survey answers, and requests, then point you to the responses behind its answer.

Follow the thread into a person’s activity, with anonymous and signed-in users kept distinct.

Where the story starts

“I found the trail, but couldn’t work out how to download it.”Feedback · Signed-in user

“Does saving a route mean I can use it offline?”Survey answer · Anonymous user

Make the next step easier to find.

These two responses suggest that the download action needs a clearer introduction.

Illustrative responses, not live customer data.

Keep the whole story moving.

Give your agent the context once. Review related requests, prepare a roadmap update, and turn what shipped into a release note customers can understand.

See the proposed changes and who could be notified before you approve them.

Offline maps, from idea to updateExample workflow

Customer request
“Let me take my routes offline.”
Read the request and related comments.
Roadmap
Make the next step visible.
Prepare a status update for the selected item and linked requests.
Changelog
Your routes. Even without a signal.
Draft a release note when the feature is ready to share.

Review each change in the conversation.

What will you ask your agent to do?

Find the context, prepare the work, and choose what happens next.

“What are people struggling with when they try offline maps? Show me the evidence.”

Example findings

The download action is hard to find.

These responses point to a discovery problem, rather than a problem with the map itself.

Feedback: “I couldn’t work out how to download it.”
Survey answer: “Does saving a route mean it works offline?”
Suggested next step: Explain where to download a saved route.

Your agent can search feedback, answers, requests, and published content, then read the sources behind a finding.

Illustrative example. No workspace data is read or changed.

“What happened before this customer asked for help with offline maps?”

Example customer context

They saved a route. Then asked how to download it.

Bring observed activity and customer responses into the same conversation.

Identity: Signed-in customer, with an explicitly linked earlier visit.
Observed activity: Opened a trail and saved the route.
Their question: “Can I use this when there’s no signal?”

Works with anonymous and identified users. Missing activity stays unknown; your agent should not fill in the gaps.

Illustrative example. No workspace data is read or changed.

“Prepare a short message showing people how to download a route. Keep it unpublished.”

Example draft

Your next adventure. Now offline.

Open a saved route and tap Download. Your map will be ready when the signal ends.

Action: Open saved routes
Style: Use the app’s existing branding.
State: Draft, ready for review.

Create questions, messages, help articles, release notes, or campaign drafts. The default mode asks for approval before saving changes.

Illustrative example. No workspace data is read or changed.

“Review these two offline-map requests and prepare a merge if they describe the same need.”

Example merge proposal

One request to follow, instead of two.

Read both requests, choose the one to keep, and see what would move before approving the merge.

Keep: Download a route for offline use
Merge into it: Use saved trails without a signal
Proposed effect: Move votes and follows; hide the duplicate.

Your agent can also update statuses and maintain roadmap items. Linked requests and potential follower notifications are part of the review.

Illustrative example. No workspace data is read or changed.

“Preview the offline-maps release note and show me what will be published.”

Example publication proposal

Offline maps are ready for your next adventure.

Give customers a clear explanation of what shipped and how to use it.

Content: The reviewed offline-maps release note.
Destination: Your Customer Portal changelog.
Next step: Confirm publication in the conversation.

Publish content, activate an experience, or manage a campaign with the required permissions. Publishing and sending have separate controls.

Illustrative example. No workspace data is read or changed.

“Why might this customer not see our offline-maps announcement?”

Example diagnosis

The message is still a draft.

Check the experience and the available customer context before trying a fix.

Message status: Draft — not eligible to appear yet.
Schedule: No active delivery window to evaluate.
On-device state: Unknown without device evidence.

Inspect status, audience rules, consent, timing, frequency limits, and push readiness. A diagnosis does not send or display anything.

Illustrative example. No workspace data is read or changed.

You set the boundaries.

Read-only: Explore customer feedback and preview possibilities.
Approve changes Default: Review the proposed action in your conversation before it runs.
Automatic: Let granted actions run under your existing permissions.

Your workspace. Your selected apps. Access you can revoke.

Delegate the work.
Keep the say.

Choose what your agent can see and do. Start with read-only access, or review its proposals before anything changes.

Publishing and sending need their own permissions. Your agent works within the access you give it.

How approvals work

Bring the agent you already work with.

Choose a connection guide to get started with an enabled workspace.

Claude

ChatGPT

Cursor

Questions about agentic workflows

What do you mean by agentic workflows?

You give your connected agent a task, and it can use UserGist to read relevant information, prepare content, and carry out permitted changes. You can stay in the conversation as the work moves forward.

Can I connect my existing assistant?

The documentation includes connection guides for Claude, ChatGPT, and Cursor using MCP. Availability depends on your client, its account policies, and an enabled UserGist workspace. Hosted connections are still in rollout.

Will it make changes without asking?

Approve changes is the default mode: product changes, including draft edits, are proposed for confirmation in your conversation. You can also choose Read-only or explicitly enable Automatic for permitted actions. Your assistant may ask for its own confirmation.

What information can my agent see?

Only information allowed by the workspace, apps, capabilities, and member role connected to it. Returned customer information is shared with your chosen assistant, so use an account and data policy appropriate for your team.

Can it understand feedback from people who haven’t signed in?

Yes. Your agent can work with anonymous and identified users and their available responses. These remain distinct identities unless your app has explicitly linked them.

Does this replace installing UserGist?

No. Your SDK connection still collects events and responses and shows experiences in your product. Agentic workflows give you another way to work with that information and manage content.

Is it available in my workspace yet?

Rollout is in progress. A configured hosted environment and an enabled workspace are required. Check AI connections in your workspace settings, or ask your workspace administrator about availability.

You’re building something great.
Let your users be part of it.

Bring feedback, surveys, messaging, and your customer portal together.

Start free

All features included.

Your customers speak.Your agent gets to work.

An answer with the customer still in it.

Keep the whole story moving.

“Let me take my routes offline.”

Make the next step visible.

Your routes. Even without a signal.

The download action is hard to find.

Delegate the work.Keep the say.

You’re building something great.Let your users be part of it.

Your customers speak.
Your agent gets to work.

Delegate the work.
Keep the say.

You’re building something great.
Let your users be part of it.