<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Raise a Query on WebNotes</title><link>https://v2.webnotes.in/tags/raise-a-query/</link><description>Recent content in Raise a Query on WebNotes</description><generator>Hugo</generator><language>en-IN</language><lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://v2.webnotes.in/tags/raise-a-query/index.xml" rel="self" type="application/rss+xml"/><item><title>How to create a support ticket at Zerodha</title><link>https://v2.webnotes.in/how-to-create-ticket-zerodha/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-create-ticket-zerodha/</guid><description>&lt;p&gt;To create a support ticket at &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
, open the help article that matches your issue on the support portal at support.zerodha.com, scroll to the bottom, tap Create ticket, choose whether to log in, describe the problem in the Describe your issue in detail box, attach up to six files under 5 MB each, and submit. Zerodha issues a ticket number and replies within 48 working hours.&lt;/p&gt;
&lt;p&gt;The ticket is Zerodha&amp;rsquo;s primary support channel, ahead of the phone line, because it leaves a written, trackable record of the query and routes it to the team that owns the topic. Zerodha does not run a single open contact form on its home page; instead the Create ticket button sits at the foot of each help article, so the article you choose sets the ticket&amp;rsquo;s category and the team it lands with. That design is the single thing most people get wrong, and it is the reason a ticket sometimes feels misrouted: the category came from the article, not from anything you typed.&lt;/p&gt;</description></item></channel></rss>