Changelog

We've added workspace memory for Custory AI, powered by Supermemory. AI can now retrieve relevant knowledge from the current workspace so it has more context from earlier conversations, agent work, and connected journey activity when helping your team make decisions. [Open Custory AI →](https://app.usecustory.com) ## What's New **Workspace-scoped memory.** Custory stores useful AI and workspace context against the workspace it belongs to, not as one global pool. That means the assistant can build continuity around the journeys, decisions, preferences, and follow-up work in the space your team is actually using. **Relevant retrieval during chat.** When you ask Custory AI for help, it can search workspace memory and bring back the most relevant context for the request. If the chat is tied to a journey, the retrieval can also favor memory connected to that journey before falling back to broader workspace knowledge. **Supermemory-backed ingestion.** New chat messages and supported workspace context can be synced into Supermemory with metadata like workspace, journey, source type, and source ID. Custory tracks the sync status so memory sources can move through ready, failed, deleted, and related states instead of disappearing into an untracked black box. **Memory control per chat.** The assistant now includes a Memory toggle. Keeping it on lets Custory AI use workspace context for the current chat. Turning it off skips retrieval for that chat when you want a narrower answer. ## Why it matters AI is most useful when it works from the same context as the team. Without memory, every request starts closer to a blank page. With workspace memory, Custory AI can carry forward more of what the team has already learned, decided, and discussed. For lean teams, that means less repeated explanation, fewer lost details, and a clearer path from customer signal to product action. The journey stays closer to a living system your team can build from, not a set of disconnected conversations that have to be reassembled every time.

We've added PostHog and Stripe as automation-ready signal sources so your team can respond to real product usage and revenue movement without monitoring those tools separately. Instead of checking dashboards, spotting changes, and manually translating them into journey work, Custory can now pull those signals into automations and help your team act faster. Connect from [Manage Integrations](https://app.usecustory.com/manage-integrations) under **Analytics & Revenue**, then use them inside [Automations](https://app.usecustory.com/automations). ## What's New **PostHog snapshots.** Custory can now pull structured analytics snapshots from PostHog — event volume changes for a specific product event, and top events in a selected window. This helps you spot shifts in usage that may signal onboarding friction, stronger activation, feature adoption changes, or unexpected drop-offs. **Stripe monitoring.** Custory can now pull structured Stripe snapshots for subscription activity, payment failures, and refund activity — giving teams a clearer view of the commercial side of the customer journey, especially where churn risk or refund patterns point to deeper product or experience problems. **Structured summaries with severity.** Each analytics action returns more than raw numbers. Custory creates a summary with a headline, plain-language explanation of what changed, comparison windows, key metrics, a severity signal, and a recommended item type for follow-up. Instead of asking "did something change?", your team gets a clearer answer to "what changed, how serious is it, and what should we do next?" These signals are designed to work with the rest of your automation steps. After fetching a PostHog or Stripe snapshot, you can create a new insight in Custory, open a Jira, Linear, or GitHub task, or send a Slack message to the team — so the signal immediately becomes tracked follow-up work inside the same workflow. ## Why it matters Good teams don't just map customer experience — they watch for evidence that the experience is changing. With PostHog and Stripe connected to automations, Custory helps you move from passive reporting to active response. Important usage and revenue signals can shape the journey while there's still time to do something about them.

We've added Automations so your team can stop manually chasing follow-up work every time something changes in a journey. Instead of noticing an update, opening other tools, writing the same handoff context again, and posting a status message by hand, you can define a workflow once and let Custory run it for you. [Open Automations →](https://app.usecustory.com/automations) ## What's New **Scheduled automations** run on a set interval — hourly, daily, or weekly — for recurring rhythms like morning summaries, weekly review loops, or regular cleanup and follow-up. **Event-based automations** trigger the moment something important happens: a Custory item is created or updated, a status changes, impact or effort crosses a threshold, or a GitHub pull request is opened or merged. Combined with scoped filters — by journey, item group, status, impact, effort, changed fields, or GitHub repository — these automations stay focused on changes that actually matter. **Multi-step actions** let each automation chain follow-up actions together so one trigger can create momentum across tools. A single workflow can create a new Custory item, open a Jira, Linear, or GitHub issue, and send a Slack update to the team. For actions like creating items, tasks, or sending messages, AI-drafted payloads mean Custory can write clearer issue titles, better handoff descriptions, and more useful updates based on journey context. **Visibility and control.** Review validation issues before an automation runs, see run history, run scheduled automations manually, pause workflows without deleting them, and reactivate them when the team is ready. ## Why it matters The value of journey mapping isn't just seeing the problem — it's turning what you learn into action while the context is still fresh. Automations help your team do that consistently, so important insights don't get stuck in the map. They move into execution.

We've improved linked task syncing so follow-up work in external tools stays more visible inside Custory after the task is created. Creating a task is only the first part of the job — teams also need to know whether it moved, stalled, changed scope, or quietly drifted away from the original customer problem. See this in action on any linked task in your [journey editor](https://app.usecustory.com). ## What's New **Status sync.** Custory now keeps cached task status more current after work changes in Jira, Linear, GitHub, and Notion. Implementation progress stays visible without leaving the journey every time. **Title sync.** If the external task changes title, Custory can reflect that change too — which matters when work evolves and the original wording no longer matches the current implementation scope. **Notifications for external changes.** When linked work changes outside Custory, participants can be notified about important updates such as status or title changes. This helps teams avoid the common problem where implementation moves forward but the people managing journey context don't realize it. ## Why it matters Journey work loses value when the map says one thing and the delivery tools say another. External task sync updates help keep those systems closer together so your team has a more reliable view of what is happening, what changed, and what still needs attention — without manually reconciling multiple tools.

We've added personal Slack and Discord account linking so workspace notifications can reach the right person directly — not just the right channel. When a fast response depends on an individual actually seeing the update, a shared team channel isn't always enough. Set it up from [Settings → Notifications](https://app.usecustory.com/settings). ## What's New Each user can now connect their own Slack or Discord identity to their Custory account, tying notification delivery to the person rather than just a workspace-level integration. Setup uses short-lived one-time link codes so you don't have to dig through extra configuration — generate a code in settings, then complete the connection from the Custory app or bot in Slack or Discord. Once linked, Slack DM and Discord DM become available delivery options inside your notification preferences. You choose which updates stay in-app and which ones reach you directly — so high-signal alerts like mentions, assignments, automation failures, and integration issues show up where you're already paying attention. ## Why it matters Teams lose momentum when important updates depend on people remembering to check the product manually. Slack and Discord account linking helps Custory fit into the communication habits your team already has, so critical updates show up where they'll actually be seen.

We've added a dedicated notification system so important activity in Custory is easier to notice, easier to route, and easier to act on. Instead of relying on one channel for everything, you can decide which updates belong in the app, which should arrive by email, and which should reach you directly in Slack or Discord. Access it from the [notification bell](https://app.usecustory.com) in the app, or configure delivery from **Settings → Notifications**. ## What's New **In-app inbox and archive.** A notification center with an inbox for active updates, an archive for older items, mark-as-read controls, and a way to open the related work directly from the notification. One place to catch up on what changed without digging through comments, items, or integrations one by one. **Channel routing by type.** Choose delivery channels per notification category: in-app, email, Slack DM, or Discord DM. Keep lower-friction updates in the app while pushing more urgent alerts to the channels your team already watches. **Fine-grained categories.** Manage alerts for mentions, discussion activity, assignments, item status changes, workspace access updates, automation reports, integration health, and external task updates — so you stay informed without turning every update into noise. **Slack and Discord DM delivery.** Link your personal Slack or Discord account from **Settings → Notifications** so Custory can send direct messages to the right person, not just a shared channel. Especially helpful for mentions, assignment updates, automation failures, and integration problems that need quick follow-up. ## Why it matters Customer journey work moves best when the right people see the right signal at the right time. Different updates deserve different levels of attention. With delivery preferences, your team can reduce notification fatigue, make sure important changes reach the right person, and stay aligned across Custory and the communication tools they already use.

We've made Custory AI a real workspace participant instead of treating it like a detached assistant floating outside the product. AI can now show up in the same collaboration flow your team already uses — with clearer context, clearer ownership, and a more natural way to ask for help without switching modes. [Try it in your workspace →](https://app.usecustory.com) ## What's New **A real workspace member.** Custory AI is represented as an actual workspace member with a consistent identity. AI collaboration now feels like part of the product's normal teamwork model instead of an add-on layer. **Mention-based collaboration.** Ask Custory AI for help directly from the conversation around the work. Instead of copying context into another tool, you can bring AI into the thread where the discussion is already happening. **Async execution with visible outcomes.** Custory AI can process requests asynchronously and post back with the result once it's finished — useful when the request involves real work like reviewing context, generating follow-up output, or carrying out a multi-step update. **Auditable runs.** AI activity is tracked, so the work doesn't disappear into a black box. Teams have more confidence when AI is being used to help with active product work. ## Why it matters AI becomes much more useful when it behaves like part of the team workflow instead of a separate destination. By making Custory AI a real workspace member, it's easier to ask for help where decisions are actually being made — with less context switching, a visible record of what was asked and what happened, and no need to leave the workflow to get support.

We've improved the way teams start new journeys in Custory, with AI-powered imports sitting inside a faster overall journey creation flow. Not every team should have to start from the same place — sometimes you want a blank canvas, sometimes a template, and sometimes you already have the source material and want Custory to turn it into a strong first draft. [Create a new journey →](https://app.usecustory.com) ## What's New **AI-powered imports from real product sources.** Custory can now create journeys from connected product context instead of asking teams to rebuild that context by hand. Import from GitHub repositories, Figma files, or Notion databases and pages — turning product discussions, designs, documentation, or implementation context into a first draft of the journey. After you choose the source, Custory uses the imported context to help generate a journey name, stages, steps, and an initial structure your team can work from. This is especially useful when a team already has a lot of information but hasn't yet turned it into a clear customer journey. **Better starting paths.** Journey creation from the dashboard now supports all three approaches: start blank for full control, use a template for common use cases, or import from a connected app when the source material already exists elsewhere. You can also search and reopen journeys already in progress from the same view. ## Why it matters One of the hardest parts of journey work is getting started with the right amount of structure. Teams often already have the raw material they need, but it's spread across tools and trapped in formats that aren't easy to turn into a journey. By improving both imports and the broader creation flow, Custory makes journey work easier to start, easier to socialize, and easier to ground in the product reality your team already knows.

We've added MCP server access so teams can connect Custory to external AI clients like Cursor, Claude, and other compatible agents using workspace-scoped credentials. This opens up a more direct way to use Custory from the AI environments many teams already work in, while keeping access tied to the right workspace. Set it up from [Manage Integrations](https://app.usecustory.com/manage-integrations) under **MCP Server**. ## What's New **Workspace-scoped MCP keys.** MCP access is scoped to a workspace so teams can connect external AI tools without using broad, ambiguous access patterns. Keys can be created and revoked from inside the product, making it easy to manage access over time — especially when a client is no longer in use or should stop working immediately. **Setup guidance built in.** Custory provides the practical setup details teams need, including ready-to-paste configuration snippets for supported MCP clients. This reduces the friction of getting connected and helps teams move from "this sounds useful" to "this is working" faster. **AI workflow portability.** With MCP access in place, teams can work with Custory from the AI tools they already use for broader product and engineering workflows — letting those agents work with real Custory workspace context more directly. ## Why it matters Many teams are already using external AI tools as part of how they plan, write, review, and execute work. MCP Server Access helps Custory plug into that reality more cleanly, so the product can participate in those workflows without forcing teams into a disconnected setup.

We've added a shared feedback board so product feedback can live in one visible place instead of being scattered across private messages, support threads, and disconnected notes. This gives your team and your users a clearer way to see what's been reported, what others care about, and how requests are progressing over time. [Open the Feedback Board →](https://app.usecustory.com/feedback) ## What's New **One shared place for product feedback.** Instead of feedback living in isolated channels, the board gives everyone a common place to see what's already been raised — so users don't wonder whether something was reported before, and teams don't have to piece together signals manually. **Board and list views.** Feedback can be browsed in a board-style view organized by category, or reviewed in a list view for more systematic filtering. Useful for both quick discovery and deliberate product review. **Likes, subscriptions, and importance voting.** Users can like feedback they agree with, subscribe to stay updated, and vote on importance — surfacing not just what was said, but what matters most to the people around the product. **Comments and discussion.** Each feedback post carries its own discussion so teams can ask follow-up questions, clarify requests, and keep the conversation attached to the feedback itself. ## Why it matters When feedback is fragmented, teams lose important signal — the same request gets repeated, support context stays hidden, and people can't see whether others care about the same thing. A shared board changes that by turning isolated messages into visible product signal that's easier to prioritize, easier to discuss, and harder to ignore.

We've added version history so teams can revisit earlier journey states, understand how the map changed over time, and recover work more safely when needed. This gives teams the confidence to explore, revise, and clean things up without worrying that a bad edit will erase useful thinking. Open it from the **Version History** option in the [journey editor](https://app.usecustory.com) menu. ## What's New **Automatic snapshots.** Custory now saves journey snapshots at session start, session end, autosave points, milestone moments, and manual saves — giving teams a stronger safety net while the journey is evolving. **Version browsing and preview.** You can review earlier versions before restoring them, which makes history more useful than a simple rollback button. Teams can compare where the journey was and decide whether going back is the right move. **Version labels.** Important versions can be labeled so teams can identify them easily later — useful for workshop outcomes, major reframes, review checkpoints, or "before we changed the structure" milestones. **Safer restore flow.** Before restoring an older version, Custory saves the current state first. You get a safer path backward without losing the present version in the process. ## Why it matters Journey maps are living documents, and living documents change a lot. Version History & Restore gives teams more confidence to improve the map without fearing that structure, progress, or previous insight will disappear if they make the wrong edit.

We've added a dedicated persona-focused AI workflow so teams can use Custory AI to build and improve personas — not just work with journey items. This is designed for teams that want help turning rough customer knowledge into clearer persona profiles without starting from a blank page every time. Open it from the [Personas page](https://app.usecustory.com/personas) or from any journey's Personas view. ## What's New Custory AI now operates in a persona-focused mode tailored for creation, refinement, and journey linking as first-class tasks. You can ask it to create new personas, improve existing ones, add goals, frustrations, and motivations, and make personas more specific and useful. For products with several distinct user types, batch persona creation can help generate a strong starting set all at once. Persona work no longer has to stop at drafting — AI can help identify which personas matter most for a specific journey and connect them accordingly. ## Why it matters Personas often fail because they either never get created well, or they get created once and never become part of real workflow again. Custory AI for Personas closes that gap by making creation faster, refinement easier, and journey linking more natural inside the product — so user context stays alive where it actually shapes decisions, rather than sitting in a separate document no one revisits.

We've expanded GitHub into a deeper workflow connection inside Custory — not just a place to send a task once and forget about it. Teams can now connect repository context, create linked GitHub issues, monitor pull requests, and use GitHub activity as part of automations. Connect from [Manage Integrations](https://app.usecustory.com/manage-integrations) under **Product Management**. ## What's New **Linked GitHub issues.** Create GitHub issues from Custory work and keep them attached to the relevant journey step or item, so engineering follow-up stays connected to the customer context that created it. **Repository-aware setup.** Custory works with your connected repositories so issue creation and GitHub-based workflows feel grounded in your actual codebase rather than abstract references. **Pull request visibility.** GitHub pull request activity is now part of the workflow surface, making it easier to connect delivery progress back to journey work. **GitHub-driven automations.** Use GitHub pull request events — PRs being opened or merged — as automation triggers. Code activity can now drive follow-up work in Custory instead of product teams needing to notice progress manually. ## Why it matters Customer journey work often breaks down at the handoff into engineering. By connecting GitHub more deeply into Custory, that handoff becomes easier to trace, easier to automate, and easier to keep tied to the original customer problem — so product and engineering stay aligned around what changed and why.

We've added linked item relationships so teams can connect the logic inside a journey instead of leaving each insight, opportunity, and solution isolated on its own. Open any saved item in the [journey editor](https://app.usecustory.com) and use the **Insights**, **Opportunities**, and **Solutions** tabs to search and link related items from the same journey. ## What's New You can now create explicit relationships between related items — an opportunity linked to the insight that revealed it, a solution linked to the opportunity it addresses, or multiple related ideas connected around the same customer problem. Linking happens directly from inside the item so you don't have to build relationships elsewhere and then bring them back. Once linked, related items are visible on the item itself, making the chain from evidence to action much easier to follow. This turns Custory into a more useful decision-making tool, not just a place to collect observations. ## Why it matters The more work a team captures, the easier it becomes to lose the story connecting it all. Linked insights, opportunities, and solutions preserve that story — so decisions stay easier to defend, easier to revisit, and easier to move forward with confidence. When the question becomes "which insight led us here?" or "are we solving the right thing?", the answer is already attached to the work.

We've made the [journey editor](https://app.usecustory.com) more comfortable to work in day to day. This update is about improvements that may look small individually but make a real difference once a team is inside the product every week: the editor remembers how you like to work, you can control how much information is shown at once, and the table view becomes a much stronger place for review and cleanup. ## What's New **Saved view preferences.** Custory now remembers the last journey view you were using, so you don't have to reset the workspace every time you come back. If one person prefers the table for review work and another prefers the visual layout, the editor adapts more naturally to how each person works. **Property visibility controls.** Teams can now simplify or expand what's shown across cards and structured views by controlling which properties stay visible. Useful for reducing noise during workshops, showing only the fields that matter for a review, or expanding detail for more precision-oriented work. **Stronger table view.** The table view now supports searchable rows, sorting by key fields, filtering alongside the rest of the editor, and better handling for long item lists. This makes it much more useful when the job is auditing and cleaning up the journey rather than presenting its story. ## Why it matters The best workflow improvements are often the ones that quietly save time every single session. Remembering view preferences, letting teams control visible properties, and giving them a better table workflow all reduce friction in the moments that happen every day — reopening a journey, switching between discussion and audit work, reviewing long item lists. Less energy managing the interface means more energy improving the journey.

We've improved the way teams find and narrow down work inside a journey. As journeys grow, the problem usually isn't that teams captured too little — it's that the right item becomes harder to find in the moment. This update makes search and filtering much more useful when working inside a larger map. Find these controls at the top of any [journey editor](https://app.usecustory.com). ## What's New **Hybrid search.** Custory now combines exact-text search with semantic search, surfacing relevant items even when the wording isn't an exact match. In real team workflows, people often remember what a problem *meant* rather than the exact title someone wrote weeks ago. This makes search much more forgiving and practical once a journey has real content. **Stronger filters.** The new filter flow makes it easier to narrow the map down to exactly what matters for the conversation in front of you — filtering by ownership, status, type, priority, impact, effort, and group context. Instead of treating the whole journey as one giant surface, you can isolate the part that matters right now. **Active filter awareness.** The editor makes active filtering more visible, so teams can immediately tell whether they're looking at the full map or a narrowed working view. A subtle detail, but one that matters in practice. ## Why it matters Customer journey maps get more useful as they grow, but they also get harder to navigate if the product doesn't help teams focus. With hybrid search and better filters, Custory helps large journeys feel less overwhelming and much more operational — turning "there is a lot here" into "here is exactly what we need to look at."

We've expanded the way teams can work inside a journey. Instead of forcing every job into one layout, Custory now lets you move between different views depending on what you're trying to do — understand the story, clean up the data, prioritize work, or review progress. All views share the same search, filters, and property visibility settings so you stay focused as you switch. [Open a journey to try it →](https://app.usecustory.com) ## What's New **Journey view** remains the best way to understand the customer flow across stages and steps — the natural starting point for workshops, narrative reviews, and seeing the experience as a whole. **Grid view** gives teams a more operational surface for scanning and managing work in a structured layout. Useful when you want to review groups, spot gaps, and interact with items without the full narrative context. **Table view** makes it easier to work through larger journeys with sorting, filtering, and searching by type, status, priority, impact, effort, stage, and step. This is the view for audit work and cleanup, not storytelling. **Impact / effort matrix** gives teams a dedicated space to compare items by impact and effort — when the question shifts from "what is happening?" to "what should we act on first?" ## Why it matters Most teams eventually outgrow a single way of looking at the journey. With multiple views in the same editor, Custory helps teams move from understanding, to review, to prioritization, to follow-through — without exporting the work somewhere else just to keep moving.

We've made items much more useful as places to work, not just places to label something. Instead of keeping context for an insight, opportunity, or solution spread across files, screenshots, chat messages, and follow-up notes, teams can now keep all that supporting material directly on the item itself. Open any item in the [journey editor](https://app.usecustory.com) to access the **Details** tab. ## What's New **File attachments.** Upload supporting files — screenshots, exported evidence, documents, customer examples — directly to an item. The proof stays with the item it supports instead of living somewhere else. **External links with context.** Items can now include external links with titles and descriptions, pointing to relevant docs, tickets, recordings, or dashboards while keeping the item as the central place to work. **Image gallery.** Image attachments are surfaced as a browsable gallery inside item details, making it much easier to review screenshots, UI references, or customer-submitted visuals without digging through downloads. **Comments on the item.** Teams can discuss the item directly where the work lives — keeping clarifications, follow-up questions, and decisions attached to the actual insight or opportunity rather than scattered across chat threads. **AI activity context.** Custory surfaces pending AI activity on the item so teams can see when related work is still in progress, reducing uncertainty about whether something happened. ## Why it matters The quality of a journey map depends on how easy it is to trust, revisit, and act on what the team captured. Rich item details help with that by keeping evidence, discussion, and supporting material close to the customer problem — so teammates can pick up work without a separate handoff, and decisions stay easier to understand long after they were made.

We've added a more complete personas system so teams can manage personas across the workspace and connect them directly to the journeys they influence. Instead of becoming disconnected documentation nobody revisits, personas can now live close to the journey work they're meant to inform. [Open Personas →](https://app.usecustory.com/personas) ## What's New **Workspace-level personas.** Create and manage personas as first-class records in the workspace — not scattered notes — from the [Personas page](https://app.usecustory.com/personas). **Journey linking.** Personas can be linked directly to the journeys where they matter most, keeping the right customer lens attached to the right journey without relying on people to remember it from somewhere else. Teams can create a new persona and link it to a journey as part of the same action. Once created, personas can be refined over time as your product, users, and understanding evolve. ## Why it matters Personas are most helpful when they sharpen decisions — not when they become another disconnected artifact. By giving personas a proper workspace and journey-linking model, Custory makes them easier to use where they actually create value: inside real mapping and prioritization work, attached to the experiences they describe.

We've expanded Slack and Discord from simple notification destinations into real collaboration surfaces for Custory AI. Your team can now ask Custory AI for help directly inside a Slack or Discord thread and keep that conversation tied back to the relevant work in Custory. Connect your workspace from [Manage Integrations](https://app.usecustory.com/manage-integrations). ## What's New Custory AI can now respond to requests made directly inside Slack and Discord conversations, keeping context from the ongoing thread so responses are grounded in the real discussion — not just a single isolated message. When a conversation maps to real work, Custory connects the thread to the relevant item so context doesn't get scattered across external chat. AI-generated follow-up can be written back into Custory, keeping the reasoning, request, and outcome close to the journey work itself. This is especially useful for teams that operate heavily in chat: you can ask for help mid-conversation, turn a discussion into a tracked item more quickly, and reduce the copy-paste gap between conversation and action. ## Why it matters Many teams notice the problem in Slack or Discord first, but important context often gets lost before it becomes structured work. AI collaboration threads help bridge that gap — so the conversation can stay fast while the resulting work stays connected and usable inside Custory.

You can now share customer journey insights, updates, and notifications directly with your team through Slack and Discord. Connect both tools from [Manage Integrations](https://app.usecustory.com/manage-integrations) and choose which channels should receive updates. ## What's New **Slack integration.** Post journey map updates to dedicated Slack channels, share pain point discoveries and resolution progress, and send automated notifications when tasks are created or completed — with rich previews and direct links back to the journey. **Discord integration.** Share journey milestones and automated updates in Discord channels, create rich embeds with journey map previews and direct links, and support both public channels and private threads. Both integrations support automated notifications for new pain points, task status changes, journey completions, and team mentions — as well as on-demand sharing from any journey step or section when you want to add more context before posting. ## Why it matters Your team doesn't only work inside Custory. These integrations make sure important journey signals reach people in the tools they already watch, so updates don't get missed and follow-up can start immediately.

We've added integrations with Linear and Jira so your team can create and sync tasks between customer journey maps and your project management tools — without losing the customer context that created the work. Connect from [Manage Integrations](https://app.usecustory.com/manage-integrations) to get started. ## What's New **Linear integration.** Create Linear issues directly from customer journey steps, with context preserved and issues linked back to their source. Select teams, labels, and priorities when creating issues, and view linked tasks as badges directly on your journey steps. **Jira integration.** Connect Jira projects to Custory for comprehensive task management. Create issues from pain points and opportunities, sync status and priority updates automatically, and maintain bidirectional links between journey steps and Jira tickets. Issue statuses sync regularly so implementation progress stays visible without leaving the journey. To connect: go to workspace settings, click **Add Integration**, select Linear or Jira, and authorize through OAuth. Then create tasks from any journey step using the AI action button — the task is created instantly with a link back to the journey. ## Why it matters Customer insight that doesn't move into tracked execution loses its value quickly. These integrations close that gap by connecting the problems identified in Custory directly to the tools where engineering and product teams already manage follow-up work. Your credentials are encrypted, stored securely, and protected by OAuth 2.0 with granular permission scopes.

We've improved how teams collaborate inside Custory so working in the same journey feels more natural, more visible, and less chaotic. Collaboration now happens closer to the work itself — with presence signals in the [journey editor](https://app.usecustory.com) and comments attached directly to each item. ## What's New **Comment threads on items.** Comments now live directly on journey items, keeping decisions, clarifications, and follow-up questions next to the actual insight or opportunity being reviewed. Context is easy to lose when discussion happens somewhere else — with attached comments, the reasoning stays easy to revisit. **Live presence signals.** The journey editor now shows presence avatars so teammates can see who else is currently viewing or working in the same journey. It helps reduce collisions, makes collaboration feel more alive, and gives teams more confidence when editing together. **Real-time editing cues.** Alongside presence avatars, Custory also shows live cursor activity while teammates are working on the map, making shared editing feel more immediate. ## Why it matters Real-time collaboration isn't only about multiple people editing at once. It's also about reducing uncertainty while they work. With comments on items and live presence signals, Custory helps teams keep discussion closer to the work, avoid losing context across tools, and make shared editing feel safer and easier to follow over time.

We've improved the way teams set up, manage, and collaborate inside shared workspaces in Custory. This update is about making the workspace feel like the real shared home for the team — so the right people can find it, join it, and start contributing with less friction. [Open your workspace →](https://app.usecustory.com) ## What's New Custory now supports domain-based workspace discovery, owner-email lookup when the right workspace isn't found automatically, and request-to-join flows inside the product. In-app invitation alerts with accept and decline actions reduce the back-and-forth before collaboration even begins. Once people are in, workspace management includes role-based permissions, clearer invitations, and a more direct path into the shared space where work happens. Multiple workspaces make it easier to separate clients, departments, product lines, or internal and external work cleanly. ## Why it matters When workspace setup is confusing, collaboration breaks down early. People miss invites, end up in the wrong space, or depend on someone to get them oriented before they can contribute. By improving discovery, invitations, and access flows, Custory makes it easier for teams to get into the right shared space and start working together sooner.

We've made major improvements to the AI engine that powers contextual suggestions throughout your journey mapping workflow. The AI now understands the full context of your journey map, delivering more relevant and actionable suggestions as your team works. [Try it in the editor →](https://app.usecustory.com) ## What's New The AI now provides richer support across touchpoint recommendations, pain point identification, emotion mapping, and opportunity discovery. Suggestion generation is significantly faster, with better understanding of industry-specific terminology. The AI also offers deeper pain point analysis by spotting patterns across multiple journeys, suggesting root cause questions, and recommending potential solutions. Simply start typing in any field and the AI will provide contextual suggestions based on your journey's current state. The more context your journey contains, the more useful those suggestions become. ## What's next Upcoming improvements include automatic journey map generation from customer interviews, sentiment analysis for customer feedback, and predictive analytics for identifying journey bottlenecks. Stay tuned for more updates.

We've added the first version of the Custory journey editor — the core workspace for building and evolving customer journeys inside the product. Instead of mapping experiences in disconnected tools, teams can now work directly in a structured editor designed around stages, steps, and journey items. [Open the journey editor →](https://app.usecustory.com) ## What's New Create or open a journey to start working in the editor. From there, your team can build the structure of the journey, add stages and steps, and capture observations, opportunities, and follow-up work directly inside the map — not in separate places. Journeys are organized into clear stages and steps so the team can map the flow of the customer experience in a way that is easier to understand and discuss. Items live directly on the map, keeping all the relevant context close to the work itself. ## Why it matters The first challenge in journey work is often just having one shared place to do it. With the journey editor, Custory gives teams a foundation they can actually work in together. It becomes easier to capture what is happening, discuss where the experience breaks down, and start improving the journey without recreating the same context across multiple tools. This release lays the groundwork for everything that comes next.