# Understand Collection rules

Collection Rules allow you to precisely control *when* and *under what conditions* feedback is requested. By defining a targeted collection strategy, you can optimize response rates and ensure a seamless customer experience.

Each Feedback Survey maintains its own independent rule set, giving you total flexibility across different touchpoints.

#### Available Rule Types <a href="#available-rule-types" id="available-rule-types"></a>

Currently, Myra offers the following Collection Rules to trigger your surveys:

* **Date Range**
  * Restrict feedback collection to a specific, predefined timeframe.
* **Day of Week**
  * Limit feedback requests to specific days (e.g., Monday through Friday).
* **Always Allow**
  * Keep the feedback channel open permanently.
* **Last Submission**
  * Users can only submit a new review after the given period of time has passed since their last response.
* **Last Resolved**
  * Require the user to have at least one Jira issue resolved within a specific timeframe before they are prompted for feedback again.
* **Request Closed**
  * Feedback can only be submitted once the associated Jira request has been closed.
* **Reporter Only**
  * Restrict survey access exclusively to the original creator (reporter) of the Jira issue.

#### Configuring Your Rules <a href="#configuring-your-rules" id="configuring-your-rules"></a>

To manage your collection strategy, navigate to the **Settings** tab and scroll down to the **Collection Rules** section.

1. **Enable Collection:** You must first toggle Feedback Collection to "On" within the Settings page before any rules can take effect.

<figure><img src="/files/6mJeMxzPmruUSIUgenUZ" alt="" width="563"><figcaption><p>Enable collection</p></figcaption></figure>

{% stepper %}
{% step %}

### **Add a Rule**

**Add Rule** button and select your desired Rule Type.

<figure><img src="/files/CIleIDv2G7lXiKn83usH" alt="" width="563"><figcaption><p>Add new rule</p></figcaption></figure>

<figure><img src="/files/ruHztaIY09jX0SMP9puD" alt="" width="375"><figcaption><p>Select Rule Type (CSAT specific rules shown)</p></figcaption></figure>
{% endstep %}

{% step %}

### **Name and Describe**

Assign a unique name to your rule. (*Rule names cannot be changed once saved.)* We highly recommend adding a short description to document the rule's purpose for your team.

<figure><img src="/files/XOxHExG7UCfqVgJbpdP6" alt="" width="375"><figcaption><p>Add a unique name, add a short description</p></figcaption></figure>
{% endstep %}

{% step %}

### **Toggle Status, Configure, Delete**

Once created, each rule can be independently switched on or off, allowing you to pause or resume specific conditions without deleting them. Also each rule can be configured and deleted.

<figure><img src="/files/Lib6ZhUpZ5sNrB8IzCr7" alt="" width="563"><figcaption><p>Delete, Configure, Toggle rule status</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Default CSAT collection rules cannot be deleted!
{% endhint %}

**Default Behavior:** When you create a new Feedback Survey, an **Always Allow** rule is applied by default. You can delete this at any time to build a custom rule set.

If Feedback Collection is turned "On" but *all* Collection Rules are deleted (or turned off), **the survey will not appear.** You must have at least one active Collection Rule defined for a survey to trigger.

#### Rule & Scope Compatibility Matrix <a href="#rule-and-scope-compatibility-matrix" id="rule-and-scope-compatibility-matrix"></a>

Because Myra Feedback Surveys can operate under different scopes (Request, Project, Public), not all rules are applicable in every context. Reference the compatibility matrix below to see which rules can be applied to your specific scope:

<table><thead><tr><th></th><th>Request scope</th><th>Project scope</th><th width="145">Public scope</th><th>CSAT</th></tr></thead><tbody><tr><td><strong>Date range</strong></td><td>🟢</td><td>🟢</td><td>🟢</td><td>🟢</td></tr><tr><td><strong>Day of week</strong></td><td>🟢</td><td>🟢</td><td>🟢</td><td>🟢</td></tr><tr><td><strong>Always allow</strong></td><td>🟢</td><td>🟢</td><td>🟢</td><td>🟢</td></tr><tr><td><strong>Last submission</strong></td><td>🟢</td><td>🟢</td><td>🔴</td><td>🔴</td></tr><tr><td><strong>Last resolved</strong></td><td>🟢</td><td>🟢</td><td>🔴</td><td>🟢</td></tr><tr><td><strong>Request closed</strong></td><td>🟢</td><td>🔴</td><td>🔴</td><td>🟢</td></tr><tr><td><strong>Reporter only</strong></td><td>🟢</td><td>🔴</td><td>🔴</td><td>🟢</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/understand-collection-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.