Guidelines for Support Agents on Product Roadmap Access and Customer Requests

Guidelines for Support Agents on Product Roadmap Access and Customer Requests

This page provides a reusable support reference for cases in which customers request access to product roadmap details, feature timing, or internal planning visibility. It is based on a resolved BigPicture support case and is intended to help support agents respond consistently, set expectations clearly, and coordinate approvals when limited roadmap information may be shared.

Use this guide when a customer asks for roadmap access, release timing, screenshots of planned functionality, or confirmation that specific feature gaps are being addressed.

When to Use This Playbook

  • Customer is evaluating the product and wants roadmap visibility before a decision, bid, or client presentation.

  • Customer asks for access to an internal roadmap page or planning document.

  • Customer wants ETA commitments for features still under evaluation.

  • Customer requests screenshots, descriptions, or evidence that known gaps are being actively addressed.

  • Support needs to align with Product Management before sharing anything beyond standard public messaging.

Case Summary

In the reference case, the customer was preparing a major bid involving Appfire PPM capabilities and wanted more detail on roadmap items that were not visible externally. The main interest area was financial management capabilities and whether product gaps were being addressed on a realistic timeline. The customer had also created several related feature requests to support the evaluation.

Field

Value

Field

Value

Support ticket

SUPPORT-231044

Product

BigPicture - Portfolio & Resource Management for Jira

Platform

Cloud

Request type

Question

Support category

Improvement

Customer intent

Product evaluation and bid support

Resolution

Answered

Core Support Principles

  1. Do not promise roadmap commitments. If items are in exploration or open discovery, avoid implying delivery dates or guaranteed scope.

  2. Be transparent about visibility limits. If a roadmap page is internal, say so plainly and explain that sharing is subject to internal approval.

  3. Acknowledge the business context. Customers often ask because they are making purchasing, renewal, or bid decisions. Recognize urgency without overcommitting.

  4. Offer the highest safe level of detail. If full access is not possible, consider alternatives such as a summarized response or approved PDF snapshot.

  5. Coordinate with Product before sharing artifacts. Internal drafts, screenshots, and roadmap exports should not be shared without explicit approval.

  6. Link customer requests to backlog signals. Feature requests and recurring asks should be referenced internally to help Product assess demand.

Internal roadmap content can be incomplete, draft-quality, or ambiguous across product editions. If anything is shared, include clear caveats that the material may change and may not reflect the latest planning state.

Recommended Response Flow

  1. Acknowledge the request and context.

    Thank the customer, mention the use case, and confirm you understand why roadmap clarity matters.

  2. Set the default expectation.

    Explain that roadmap items in early evaluation do not have firm ETAs and may not be externally visible.

  3. Check whether any public or semi-public material exists.

    If there is an approved summary page or standard roadmap statement, use that first.

  4. Escalate internally for sharing approval if needed.

    Ask Product Management or the relevant owner whether a PDF, summary, or limited description can be shared.

  5. Provide a safe interim update.

    If approval is pending, tell the customer what is happening and when you expect to follow up.

  6. Share only approved content with disclaimers.

    If a document is approved for sharing, explain any limitations such as draft status, incomplete coverage, or lack of distinction between editions.

  7. Close the loop.

    Invite follow-up questions and document what was shared and approved.

What Worked Well in the Reference Case

  • The agent acknowledged the customer's commercial timeline and product-evaluation context.

  • The initial response correctly explained that the requested items were in an open phase and had no ETA.

  • The agent did not grant direct access to internal content without approval.

  • Internal follow-up was performed with Product stakeholders before anything was shared.

  • An approved alternative was eventually provided as a PDF rather than unrestricted page access.

  • The customer-facing message included transparent caveats that the roadmap was not fully up to date and could change soon.

Best practice: when sharing a roadmap artifact, pair it with plain-language caveats so the customer receives useful context without mistaking draft planning for a commitment.

Risks to Avoid

  • Sharing internal roadmap pages directly without approval.

  • Giving date estimates for items that are still being evaluated.

  • Using vague optimism that sounds like a commitment.

  • Sharing screenshots or feature descriptions that expose confidential plans.

  • Forgetting to clarify differences between product editions if the roadmap does not separate them cleanly.

  • Leaving the customer without updates during an approval wait, especially when they have a same-week presentation or bid deadline.

Reusable Response Patterns

1. Initial acknowledgement

Thanks for sharing the context and the feature priorities. I understand why roadmap visibility is important for your evaluation and upcoming decision-making. Some of the items you referenced are currently under review internally, so they are not yet represented as committed delivery items with a release timeline.

2. When no ETA can be shared

At this stage, these requests are in an evaluation phase. That means the team is reviewing demand and fit, but we do not have a confirmed ETA or release commitment that we can share yet.

3. When the roadmap page is internal

The roadmap page you found is currently maintained as an internal draft, so we cannot provide direct access at this time. I am checking whether there is an approved way to share a summary or snapshot of the relevant areas instead.

4. Interim update while approval is pending

I wanted to share a quick update: I have reached out internally to confirm what level of roadmap detail we can provide. I know the timing matters on your side, and I will follow up as soon as I have a definite answer.

5. When approved material can be shared

We can share a roadmap snapshot for general planning context. Please note that it is not fully up to date, some details may change, and it may not clearly distinguish between related product editions. It should be treated as directional rather than a delivery commitment.

Decision Guide for Agents

Situation

Recommended action

Message to customer

Situation

Recommended action

Message to customer

Customer asks for ETA on uncommitted feature

Do not estimate; confirm evaluation status

Explain that there is no confirmed timeline yet

Customer asks for access to internal roadmap page

Decline direct access; seek approved alternative

State that the page is internal and approval is required

Customer has urgent bid or presentation deadline

Provide interim update quickly and escalate internally

Acknowledge urgency and commit to a follow-up

Product approves limited sharing

Send approved artifact with caveats

Clarify draft status and non-commitment

Customer lists multiple feature requests

Link requests internally to demand signals

Confirm the feedback is being tracked

Suggested Internal Checklist

Confirm whether the customer is asking for roadmap access, ETA, screenshots, or feature confirmation.
Identify whether any public or approved roadmap summary already exists.
Check whether the requested content is internal draft material.
Contact the relevant Product or strategy owner for approval.
Record any related feature requests or backlog references.
Send an interim update if approval will take time.
If sharing is approved, include disclaimers about draft status and change risk.
Document exactly what was shared in the ticket.

Internal Notes to Capture in Similar Cases

  • Customer scenario: evaluation, renewal, sales opportunity, escalation, or strategic bid.

  • Requested visibility: roadmap page, PDF, screenshots, release timing, edition-specific information.

  • Approvers consulted: Product Manager, strategy owner, or designated content owner.

  • Artifacts shared: summary statement, link, PDF, screenshot, or none.

  • Disclaimers used: draft status, possible change, lack of edition separation, no ETA.

  • Related feature request IDs or internal backlog references.

Recommended Standard Position

Support can acknowledge strategic interest, confirm that feedback is tracked, and communicate whether an area is under evaluation. Support should not independently share internal roadmap assets or imply delivery commitments. If there is a strong commercial need, the best path is to request approval for a controlled summary or snapshot and share it with clear disclaimers.

References