Prompting guidelines and examples for App Builder

<body>
<p id="docs-hc-snippet" style="display: none;">The App Builder leverages natural language processing (NLP) to interpret user prompts and transform them into actionable app components. To maximize the effectiveness of this tool, it's important to provide clear and precise prompts. This article outlines key guidelines for crafting effective prompts for communicating your needs effectively to the App Builder. It also includes some examples of how to use the App Builder prompt framework to help you narrow in on what you’re working towards.</p>
<div class="article-banners">
<div id="docs-wmp-link">
<a href="https://support.zendesk.com/hc/en-us/articles/5411234991258-plan" rel="noopener" target="_blank">What's my plan?</a>
</div>

<div class="article-banner" id="suite_pee">
<table>
<tbody>
<tr>
<td>
<strong>All Suites</strong>
</td>
<td>Professional, Enterprise, or Enterprise Plus</td>
</tr>
</tbody>
</table>
</div>

<div class="article-banner" id="support_pe">
<table>
<tbody>
<tr>
<td>
<strong>Support</strong>
</td>
<td>Professional or Enterprise</td>
</tr>
</tbody>
</table>
</div>

</div>

<div class="body">

<p class="p">The App Builder leverages natural language processing (NLP) to interpret user prompts and
transform them into actionable app components. To maximize the effectiveness of this
tool, it's important to provide clear and precise prompts. This article outlines key
guidelines for crafting effective prompts for communicating your needs effectively to
the App Builder. It also includes some examples of how to use the App Builder prompt
framework to help you narrow in on what you’re working towards.</p>
<p class="p">By following these guidelines and framework example, you can ensure that the LLM
understands your requests accurately, resulting in a smoother app development process
and better outcomes.</p>
<div class="p">This article includes these sections:<ul class="ul" id="topic_crd_rxg_s2c__ul_b2v_bhj_4fc">
<li class="li"><a class="xref" href="#topic_e12_qbx_zgc">Best practices for effective prompting</a></li>
<li class="li"><a class="xref" href="#topic_gzx_xgj_4fc">Guidelines for App Builder prompts</a></li>
<li class="li"><a class="xref" href="#topic_mzb_23j_4fc">Framework for App Builder prompts</a></li>
<li class="li"><a class="xref" href="#topic_oyq_11l_4fc">Prompt examples, using MAPS principles</a></li>
<li class="li"><a class="xref" href="#topic_bkw_d1l_4fc">Customer-built app examples</a></li>
<li class="li"><a class="xref" href="#topic_isx_z2w_djc">Additional resources</a></li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title2" class="topic nested1" id="topic_e12_qbx_zgc">
<h2 class="title topictitle2" id="ariaid-title2"><strong class="ph b">Best practices for effective prompting</strong></h2>
<div class="body">
<p class="p">Following these best practices will help you minimize the number of prompts needed
while generating more accurate and efficient results from App Builder.</p>
<ul class="ul" id="topic_e12_qbx_zgc__ul_wrv_qbx_zgc">
<li class="li">
<strong class="ph b">Focus prompts on building your app</strong>: App Builder is optimized to help you
design and refine your apps, connect APIs, and set up integrations. It provides
high-level assistance for app construction but is not a replacement for
step-by-step setup instructions. For specific tasks like finding API credentials
or connecting third-party systems via API Key or OAuth, use official
documentation or trusted resources such as Google Search or ChatGPT. This frees
up your App Builder prompts for the actual app logic and feature building.</li>
<li class="li">
<strong class="ph b">Know when to seek additional help</strong>: If you’ve tried troubleshooting the
same error several times (for example, after three or four prompt attempts) and
are still unable to move forward, <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408843597850" target="_blank">contact Zendesk Customer support</a> with
your error details.</li>
<li class="li">
<strong class="ph b">Clearly describe errors and expectations</strong>: When your app encounters an
error during testing, explain exactly what went wrong and what you expected to
happen. Detailed feedback helps the AI address the issue more efficiently.</li>
<li class="li">
<strong class="ph b">Share debugging details for unresolved issues</strong>: If repeated fixes are
unsuccessful, clearly state this in your prompt. Ask the AI to generate
extensive debugging information in the console, then reproduce the error and
paste the output back into the conversation.</li>
<li class="li">
<strong class="ph b">Batch cosmetic and simple changes</strong>: To optimize prompt usage, group minor
adjustments (such as layout tweaks, button styles, or tab order) into a single
prompt instead of sending multiple separate requests.</li>
<li class="li">
<strong class="ph b">Customize test mode with ticket search</strong>: Use the ticket search in Agent
Workspace to change tickets while testing your app. This enables quick scenario
validation without extra prompts.</li>
<li class="li">
<strong class="ph b">Provide examples for private or unknown APIs</strong>: If you’re using an API that
App Builder doesn’t recognize, include both a sample API request and the
expected response. This improves the AI’s accuracy and reduces wasted
iterations.</li>
<li class="li">
<strong class="ph b">Test in both light and dark mode</strong>: If any agents use <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/9011095783322" target="_blank">dark mode</a>, be sure to test your app in
both themes to catch and resolve visual issues early.</li>
<li class="li">
<strong class="ph b">Save your blueprint before deleting conversations</strong>: Before deleting a
conversation, save the <code class="ph codeph">blueprint.md</code> file from the Code tab. It
contains your app’s design summary and is important for future revisions.</li>
<li class="li">
<strong class="ph b">Adjust app name and icon via Settings</strong>: Update your app’s name and icon
directly in the Settings tab rather than through prompts.</li>
<li class="li">
<strong class="ph b">Apps run inside Agent Workspace</strong>: App Builder apps operate within the
Agent Workspace environment and run only while that workspace is open. If you
need background or persistent workflows, use Action Builder, ZIS, or external
tools like Workato, Zapier, AWS Lambda, or Heroku.</li>
<li class="li">
<strong class="ph b">Plan requirements before building</strong>: Outline your app’s goal, workflow,
data requirements, and preferences before you start. This helps the AI deliver a
strong first version and often results in a faster build than filing a support
ticket.</li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title3" class="topic nested1" id="topic_gzx_xgj_4fc">
<h2 class="title topictitle2" id="ariaid-title3"><strong class="ph b">Guidelines for App Builder prompts</strong></h2>
<div class="body">
<p class="p">Best practices for writing prompts when using the Zendesk App Builder, include:</p>
<ul class="ul" id="topic_gzx_xgj_4fc__ul_u1s_jhj_4fc">
<li class="li" dir="ltr">
<strong class="ph b">Use clear and simple language </strong><ul class="ul" id="topic_gzx_xgj_4fc__ul_v1s_jhj_4fc">
<li class="li" dir="ltr">Write prompts in natural, straightforward sentences as if
explaining your needs to a colleague. </li>
<li class="li" dir="ltr">Avoid technical jargon or programming terms that you do not
explain or that users wouldn’t know. </li>
<li class="li" dir="ltr">Be direct about what the app should do.</li>
</ul>
</li>
</ul>
<ul class="ul" id="topic_gzx_xgj_4fc__ul_w1s_jhj_4fc">
<li class="li" dir="ltr">
<strong class="ph b">Be specific about desired functionality </strong><ul class="ul" id="topic_gzx_xgj_4fc__ul_x1s_jhj_4fc">
<li class="li" dir="ltr">Clearly state what data sources the app should use (for
example, Google, Jira, internal database). </li>
<li class="li" dir="ltr">Specify the core features or actions the app should have (such as
display order status, submit escalation form). </li>
<li class="li" dir="ltr">Include any critical data points or outputs you want
visible.</li>
</ul>
</li>
</ul>
<ul class="ul" id="topic_gzx_xgj_4fc__ul_y1s_jhj_4fc">
<li class="li" dir="ltr">
<strong class="ph b">Include the user context or role </strong><p class="p">This helps the App Builder
tailor the interface and functionality accordingly.</p>
<ul class="ul" id="topic_gzx_xgj_4fc__ul_z1s_jhj_4fc">
<li class="li" dir="ltr">Mention the primary users of the app (for example, agents,
supervisors).</li>
<li class="li" dir="ltr">Describe the context in which they will use the app (for
example, while handling support tickets). </li>
</ul>
</li>
<li class="li" dir="ltr">
<strong class="ph b">Break down complex requests </strong>
<p class="p">This reduces errors and helps you better understand each feature.</p>
<ul class="ul" id="topic_gzx_xgj_4fc__ul_abs_jhj_4fc">
<li class="li" dir="ltr">If the app needs multiple functions, try splitting requests
into smaller parts and build iteratively. </li>
<li class="li" dir="ltr">Start with a basic app prompt, then refine by adding features
or details step-by-step. </li>
</ul>
</li>
<li class="li" dir="ltr">
<strong class="ph b">Use examples and visual expectations </strong><ul class="ul" id="topic_gzx_xgj_4fc__ul_bbs_jhj_4fc">
<li class="li" dir="ltr">If possible, describe how you want the app’s output to look
(list, button, graph).</li>
<li class="li" dir="ltr">Referencing tangible elements helps the builder create
intuitive interfaces.</li>
</ul>
</li>
</ul>
<ul class="ul" id="topic_gzx_xgj_4fc__ul_cbs_jhj_4fc">
<li class="li" dir="ltr">
<strong class="ph b">Request iterative improvements </strong><p class="p">An iterative cycle allows you
to test and improve the app one feature at a time instead of all at once,
leading to better final apps without coding.</p>
<ul class="ul" id="topic_gzx_xgj_4fc__ul_dbs_jhj_4fc">
<li class="li" dir="ltr">After the first version is generated, review and provide
feedback: what works, what doesn’t. </li>
<li class="li" dir="ltr">Use natural language to specify changes (for example, “Add a
button to refresh data” or “Show only open tickets”). </li>
</ul>
</li>
</ul>
<ul class="ul" id="topic_gzx_xgj_4fc__ul_ebs_jhj_4fc">
<li class="li" dir="ltr">
<strong class="ph b">Focus on practical benefits</strong><p class="p">This keeps the app focused on
delivering value, which ensures relevance and usability.</p>
<ul class="ul" id="topic_gzx_xgj_4fc__ul_fbs_jhj_4fc">
<li class="li" dir="ltr">Frame prompts around the problems to solve or tasks to
simplify for agents. </li>
</ul>
</li>
</ul>
<ul class="ul" id="topic_gzx_xgj_4fc__ul_gbs_jhj_4fc">
<li class="li" dir="ltr">
<strong class="ph b">Avoid ambiguity </strong><ul class="ul" id="topic_gzx_xgj_4fc__ul_hbs_jhj_4fc">
<li class="li" dir="ltr">Don’t leave vague terms like “show relevant info” without
explaining what “relevant” means. </li>
<li class="li" dir="ltr">Ambiguity can lead to apps that don’t meet your
expectations.</li>
</ul>
</li>
</ul>
<p class="p" dir="ltr">By following these best practices, users without coding experience can
write effective prompts to create useful, custom support apps. </p>
</div>
</div>
<div aria-labelledby="ariaid-title4" class="topic nested1" id="topic_mzb_23j_4fc">
<h2 class="title topictitle2" id="ariaid-title4"><strong class="ph b">Framework for App Builder prompts</strong></h2>
<div class="body">
<p class="p">When writing a prompt, you’re giving the App Builder instructions in a way that’s
similar to giving instructions to a developer to create an app for you.
It’s helpful to have a plan for what you want to accomplish. The following framework
lets you and the App Builder know what you’re expecting, which helps you focus on
what you’re working towards more effectively.</p>
<p class="p">Without this type of direction, App Builder will build an app, but it may not meet
your needs. App Builder will try, even if your prompt is <em class="ph i">Build an app</em>.
However, if you need a particular app, the more you guide the App Builder, the more
likely you’ll be to get what you need.</p>
<p class="p" dir="ltr">When writing prompts, consider these MAPS principles: Mission, Action,
Parts, Scope</p>
<ul class="ul" id="topic_mzb_23j_4fc__ul_xmt_fzj_4fc">
<li class="li" dir="ltr">
<strong class="ph b">Mission</strong>: What the app is meant to do. Consider the current need
and context.</li>
<li class="li" dir="ltr">
<strong class="ph b">Action</strong>: What the AI should generate. Consider core
functionality and workflows.</li>
<li class="li" dir="ltr">
<strong class="ph b">Parts</strong>: What the UI or structural parts are. Consider the look
and feel components.</li>
<li class="li">
<strong class="ph b">Scope</strong>: Who or what it’s for. Consider constraints and audience.</li>
</ul>
<p class="p"><img class="image img-screenshot" id="topic_mzb_23j_4fc__image_adh_xdc_wnb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/app_builder_maps.png" width="600"></p>
<p class="p" dir="ltr">By using MAPS principles, if you’re not sure or don’t like something, you
can change the action, scope, or parts without changing the other sections.</p>
</div>
</div>
<div aria-labelledby="ariaid-title5" class="topic nested1" id="topic_oyq_11l_4fc">
<h2 class="title topictitle2" id="ariaid-title5">Prompt examples, using MAPS principles</h2>
<div class="body">
<p class="p">Here are some prompt examples using MAPS principles:</p>
<p class="p"><strong class="ph b">Example 1</strong>: My Recent Satisfaction Comments app</p>
<div class="p">
<ul class="ul" id="topic_oyq_11l_4fc__ul_pyq_11l_4fc">
<li class="li" dir="ltr">
<strong class="ph b">Mission</strong>: This app is built for agent satisfaction and
allows a feedback loop for agents so that they have insight into the
customer's satisfaction history to guide interactions and improve service
quality.</li>
<li class="li" dir="ltr">
<strong class="ph b">Action</strong>: Create a side panel app that retrieves and displays
the five most recent ticket satisfaction comments and trends covering the
last six months. </li>
<li class="li" dir="ltr">
<strong class="ph b">Parts</strong>: Don’t display the date and satisfaction score.
Display the five most recent ticket satisfaction comments in a table and
6-month trends in a compact line chart. Include tabs to switch between
individual ticket satisfaction comments and trends. Make the comment column
the full width of the app. Give the background of each container a slight,
faded shade of green if the satisfaction rating was good, and a slight,
faded shade of red if the satisfaction rating was bad.</li>
<li class="li" dir="ltr">
<strong class="ph b">Scope</strong>: This app is for agents viewing support tickets.
Display ticket satisfaction comments for only the current requester and only
tickets with the same brand or organization.<p class="p"><img class="image img-screenshot" id="topic_oyq_11l_4fc__image_qyq_11l_4fc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/app_builder_customer_satisfaction_insights.png" width="600"></p>
</li>
</ul>
</div>
<p class="p"><strong class="ph b">Example 2</strong>: Customer 360 app</p>
<div class="p">
<ul class="ul" id="topic_oyq_11l_4fc__ul_ryq_11l_4fc">
<li class="li" dir="ltr">
<strong class="ph b">Mission</strong>: This app is designed to boost agent efficiency by
displaying key customer information directly within the ticket view, giving
agents quick access to the details they need to resolve issues without
navigating away.</li>
<li class="li" dir="ltr">
<strong class="ph b">Action</strong>: Create an app that retrieves and displays the
customer information, purchase history, and customer loyalty information
from our internal CRM database.</li>
<li class="li" dir="ltr">
<strong class="ph b">Parts</strong>: Display customer information, purchase history, and
customer loyalty information in 3 separate tabs. Visually indicate the tab
that is currently viewed. Highlight information in yellow if the customer
loyalty is low. Add a button to refresh the displayed data to reflect the
latest changes. </li>
<li class="li" dir="ltr">
<strong class="ph b">Scope</strong>: This app is for agents viewing support tickets.
Display this information for only the current requester and only tickets
with the same brand or organization.<p class="p"><img class="image img-screenshot" id="topic_oyq_11l_4fc__image_syq_11l_4fc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/app_builder_customer_360.png" width="600"></p>
</li>
</ul>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title6" class="topic nested1" id="topic_bkw_d1l_4fc">
<h2 class="title topictitle2" id="ariaid-title6"><strong class="ph b">Customer-built app examples</strong></h2>
<div class="body">
<p class="p">Here are some examples of apps created by Zendesk customers: </p>
<p class="p"><strong class="ph b">Assignee Change Tracket app</strong>: An app that captures all the ticket assignment
changes in a table and shows the total number of ticket assignments that happened.
This is available for admins and team leads to use. It took an admin less than 30
minutes to build this app.</p>
<p class="p"><strong class="ph b">Prompts</strong></p>
<div class="p">
<ul class="ul" id="topic_bkw_d1l_4fc__ul_ckw_d1l_4fc">
<li class="li" dir="ltr">Create an app that tracks changes on an assignee on a given
ticket. Make sure to display assignee names of previous assignees and new
assignees. Also display the total number of changes in assignment of the
ticket.</li>
<li class="li" dir="ltr">Add a button to refresh the displayed data to reflect the latest
changes. Add another button to export data to excel. Make both buttons small
and next to each other.</li>
</ul>
</div>
<p class="p"><strong class="ph b">Resulting app</strong></p>
<p class="p"><img class="image img-screenshot" id="topic_bkw_d1l_4fc__image_dkw_d1l_4fc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/app_builder_assignee_change_tracker.png" width="350"></p>
<p class="p"><strong class="ph b">My Recent Satisfaction Comments app</strong>: An app that displays the five most recent
CSAT comments on a ticket. They are intending to use this app as a replacement for
the CSAT comments that used to be displayed at the top of the ticket, which was
removed from the conversation log when they updated to the newer version of
Zendesk’s built-in CSAT tool. It took an admin one hour to build this app and deploy
it to production. This app is built for agent satisfaction and allows a feedback
loop for agents so that they know how customers are feeling after each
interaction.</p>
<p class="p"><strong class="ph b">Prompts</strong></p>
<div class="p">
<ul class="ul" id="topic_bkw_d1l_4fc__ul_ekw_d1l_4fc">
<li class="li" dir="ltr">Create an app that shows the five most recent ticket satisfaction
comments.</li>
<li class="li" dir="ltr">Update the app to only show ticket satisfaction comments for the
current user.</li>
<li class="li" dir="ltr">The app is still showing the five most recent ticket satisfaction
comments across all users rather than just the current user.</li>
<li class="li" dir="ltr">Remove the date and score columns. And make the comment column the
full with of the app.</li>
<li class="li" dir="ltr">Give the background of each container a slight, faded shade of
green if the satisfaction rating was good, and a slight, faded shade of red
if the satisfaction rating was bad.</li>
</ul>
</div>
<p class="p"><strong class="ph b">Resulting app</strong></p>
<p class="p"><img class="image img-screenshot" id="topic_bkw_d1l_4fc__image_fkw_d1l_4fc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/app_builder_my_recent_satisfaction_comments.png" width="250"></p>
<p class="p"><strong class="ph b">User Data app</strong>: An app that displays the requester’s ticket data, full ticket
history, and ticket attachments.</p>
<p class="p"><strong class="ph b">Prompts</strong></p>
<div class="p">
<ul class="ul" id="topic_bkw_d1l_4fc__ul_gkw_d1l_4fc">
<li class="li" dir="ltr">Create a Knowledge or Explore report of the user’s ticket data
where created date, closed date, and ticket ID are provided. The button for
the report should create the report first, then set it as downloadable.</li>
<li class="li" dir="ltr">See the customer’s ticket history where all ticket statuses are
shown in the order of New&gt;Open&gt;Pending&gt;Solved&gt;Closed.</li>
<li class="li" dir="ltr">Download all files sent as attachments in the ticket.</li>
</ul>
</div>
<p class="p"><strong class="ph b">Resulting app</strong></p>
<p class="p"><img class="image img-screenshot" id="topic_bkw_d1l_4fc__image_hkw_d1l_4fc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/app_builder_user_data.png" width="450"></p>
<p class="p"><strong class="ph b">My Insight app</strong>: An app that allows agent visibility into the top five ticket
topics or categories they’ve solved within the last six months.</p>
<p class="p"><strong class="ph b">Prompts</strong></p>
<div class="p">
<ul class="ul" id="topic_bkw_d1l_4fc__ul_ikw_d1l_4fc">
<li class="li" dir="ltr">Create an app for an agent to see their top five topics or
categories they’ve solved tickets in within the last six months, based on
the number of tickets within the last six months as well as based on the number of tickets by
ticket forms and what the CSAT is for each. Make the category names reflect
a B2C retail and ecommerce use case and just make up mock data. There should
be no N/A% or 100% CSAT scores. Add a column for AHT and Average Full
Resolution Time.</li>
<li class="li" dir="ltr">Add a filter that allows the agent to slice and dice the data by
period and also add an agent assignee count to each category.</li>
<li class="li" dir="ltr">Reassignments must be average, not total number, within each
category. Also, add a column of how the Avg. Resolution time compares
to the team benchmark using the green, yellow, and red traffic light system
tag.</li>
</ul>
</div>
<p class="p"><strong class="ph b">Resulting app</strong></p>
<p class="p"><img class="image img-screenshot" id="topic_bkw_d1l_4fc__image_jkw_d1l_4fc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/app_builder_my_insights.png" width="500"></p>
<p class="p"><strong class="ph b">User &amp; Org Details app</strong>: An app that displays user and org details
including custom user fields and custom organization fields with collapsible
sections.</p>
<p class="p"><strong class="ph b">Prompts</strong></p>
<div class="p">
<ul class="ul" id="topic_bkw_d1l_4fc__ul_kkw_d1l_4fc">
<li class="li" dir="ltr">Create an app that shows user and org details including all the
custom user fields and all the custom org fields.</li>
<li class="li" dir="ltr">Thanks. Would you please get the name of custom user and org
fields rather than the key? Also, let’s rename the app User &amp; Org
details.</li>
</ul>
</div>
<p class="p"><strong class="ph b">Resulting app</strong></p>
<p class="p"><img class="image img-screenshot" id="topic_bkw_d1l_4fc__image_lkw_d1l_4fc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/app_builder_user_org_details.png" width="450"></p>
<p class="p"><strong class="ph b">Ticket Pulse app</strong>: An app that displays the requester’s recent activity,
specifically the five most recent tickets with their associated information.</p>
<p class="p"><strong class="ph b">Prompts</strong></p>
<div class="p">
<ul class="ul" id="topic_bkw_d1l_4fc__ul_mkw_d1l_4fc">
<li class="li" dir="ltr">Create an app that displays the latest five tickets for the
current ticket requester. I want to display the number of the ticket and
subject and link that can be redirected to open it in new tab.</li>
<li class="li" dir="ltr">Can ticket be opened in a new tab inside Zendesk?</li>
<li class="li" dir="ltr">Can you make the UI more user friendly?</li>
<li class="li" dir="ltr">Give it another cooler name.</li>
</ul>
</div>
<p class="p"><strong class="ph b">Resulting app</strong></p>
<p class="p"><img class="image img-screenshot" id="topic_bkw_d1l_4fc__image_nkw_d1l_4fc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/app_builder_ticket_pulse.png" width="450"></p>
<p class="p"><strong class="ph b">Salesforce Account Details app</strong>: An app that displays the Salesforce account
details for the ticket requester. </p>
<p class="p"><strong class="ph b">Prompts</strong></p>
<div class="p">
<ul class="ul" id="topic_bkw_d1l_4fc__ul_okw_d1l_4fc">
<li class="li" dir="ltr">Use the Zendesk API to reach out to the Salesforce API and
retrieve the Salesforce account details for the ticket requester.</li>
<li class="li" dir="ltr">Now, for testing purposes to show how the app would look, have the
app return mock test values for each of the Salesforce fields without
actually reaching out to the Salesforce API. </li>
</ul>
</div>
<p class="p"><strong class="ph b">Resulting app</strong></p>
<p class="p"><img class="image img-screenshot" id="topic_bkw_d1l_4fc__image_pkw_d1l_4fc" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/app_builder_salesforce_account_details.png" width="200"></p>
</div>
</div>
<div aria-labelledby="ariaid-title7" class="topic nested1" id="topic_isx_z2w_djc">
<h2 class="title topictitle2" id="ariaid-title7">Additional resources</h2>
<div class="body">
<div class="p">As you get started with App Builder, you might find the following resources
helpful:<ul class="ul" id="topic_isx_z2w_djc__ul_msf_32w_djc">
<li class="li">
<a class="xref" href="https://community.zendesk.com/search?q=app%20builder&amp;tags%5B0%5D=app-builder&amp;content_type%5B0%5D=discussion" target="_blank">Browse all App Builder recipes</a>: A
collection of community-built app examples to inspire your next build.</li>
<li class="li">
<a class="xref" href="https://community.zendesk.com/topic/new?fid=18" target="_blank">Create an app recipe</a>: Share your own App Builder
creations with the community by submitting a recipe host. See the <a class="xref" href="https://docs.google.com/document/d/1DArPFHQIg04Fd-BRi6KTtpCMBS9XbjKNq8So2vYNnQg/edit?tab=t.0#heading=h.ct9afd5jnlyi" target="_blank">full instructions</a> to get
started.</li>
</ul>
</div>
</div>
</div>
<script id="docs-schema-markup" type="application/ld+json">{
"@context": "https://schema.org",
"@type": "TechArticle",
"@id": "https://support.zendesk.com/hc/en-us/articles/9037913973146",
"url": "https://support.zendesk.com/hc/en-us/articles/9037913973146",
"headline": "Prompting guidelines and examples for App Builder",
"description": "You can use the App Builder by providing clear, specific prompts following best practices and a structured framework to create custom support apps tailored to your needs and user context.",
"articleSection": "Extending Zendesk",
"datePublished": "2025-03-18T17:43:23+00:00",
"dateModified": "2026-05-06T21:09:07.442922+00:00",
"inLanguage": "en-US",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://support.zendesk.com/hc/en-us/articles/9037913973146"
},
"author": {
"@type": "Organization",
"name": "Zendesk",
"@id": "https://www.zendesk.com"
},
"publisher": {
"@type": "Organization",
"name": "Zendesk",
"@id": "https://www.zendesk.com"
},
"isPartOf": {
"@type": "WebSite",
"name": "Zendesk Help",
"@id": "https://support.zendesk.com/hc/"
},
"about": {
"@type": "SoftwareApplication",
"name": "Zendesk",
"@id": "https://www.zendesk.com"
}
}</script>
</body>