FAQs

Welcome to AXLR8 RequestTracker frequently asked questions. Please click on the links below or use the top right hand side search box.

Don’t forget that some FAQs are also common to all AXLR8 products so you may find answers in AXLR8 Staffing FAQs and by simply googling your question with “AXLR8”

FAQ Category List

Countdown

Messagestore takes a copy of all relevant email messages that enter and leave your business. For example, you might be set up to take any email to or from foi@yourorganisation.gov.uk and dataprotection@yourorganisation.gov.uk.

Messagestore then files them against the recipients and senders and the information request unique identifiers. The unique identifiers are coded into the subject lines in the email templates and the numbers and short descriptions are mail merged in.

This is described in greater detail together with “use cases”, blogs and articles on the messagestore.co.uk specialist website.

Merging IR references into the email subject line

The subject line of emails can have mailmerged data in them in the same way as you mail merge data into the body of a document.

The mailmerge templates are created and maintained in Document Template Admin.

Messagestore and Email2IR

Messagestore provides the platform for AXLR8’s Email2IR functionality. Email2IR checks Messagestore for any incoming email and creates a new IR ready for human management decisions:

  1. request type (or you can clik the “Spam” button) and
  2. the applicant (add new or allocate to a previous “frequent flier”).
AXLR8 Email2IR

If there is an exisiting IR reference in the subject line of the incoming email, then that incoming email does not create a new IR. The process checks for whether the email is about an exisiting IRs. It accomplishes this by reading the subject line. If there is and IR code in it, then it will add it to the “job bag” for that IR.

Please call if you need any training on this area or have any concerns about controlling visibility of emails for different groups of users.

Auto Email Alerts (Trigaware)

This is accomplished in Document Template Admin.
To find Document Template Admin, please select Admin menu (cog on LHS menu in the old system or Super User menu in the new UX). Then select Document Template Admin.
There you will see a list of documents already available.

Medium

  • Letter
  • Email
  • Text (SMS) Message
  • Other

File Types

The format of the email will allow it to present and send in diferent ways.

  • .RTF that can be opened by a wide variety of document readers including MS Word
  • .HTML for formatted emails with colours and different highlights, fonts, embedded hyperlinks
  • .TXT for plain text emails
  • other

Context

A mailing template may be built to work in various different contexts.

  • Contact person only (name address, etc.)
    • Reviews and appeals
  • Information Request where the dates (including due date), short descriptions, subject, exemptions, department, owners and applicants and much more information may be merged in specific to that IR.
  • Activity (task within an activity with a specific owner or team to respond in a department
  • Breach

Subject Line

The subject line determines ti a significan extent whether an email will be opened. You can mail merge fields of data into the subject line of your email template.

Managing AXLR8 Mail Merge Templates
Managing AXLR8 Mail Merge Templates

The scope for automation of tasks is enormous with smart mail merged correspondence available in a couple of clicks.

The documents created are also auto-attached to the Information Request. If you have AXLR8 Messagestore then incoming and outgoing emails will be stored against the Information Request, too.

Trigaware

There are also fully automated emails. These are in addition to the mail merged documents. They are launched by the AXLR8 Trigaware system which are preprogrammed on events. Examples include:

  • auto acknowledgement to applicants including details of their request and the due date
  • alert to the team handling responses
  • reminders at 10 and 5 days before the due date for those esponsible
  • alert when a department officer has added a File or Note to an Information Request.

Some clients have a two dozen of these set up containing alerts that change with conditions.

Trigaware auto emails are explained at length elsewhere.

Messagestore takes a copy of all relevant email messages that enter and leave your business. For example, you might be set up to take any email to or from foi@yourorganisation.gov.uk and dataprotection@yourorganisation.gov.uk.

Messagestore then files them against the recipients and senders and the information request unique identifiers. The unique identifiers are coded into the subject lines in the email templates and the numbers and short descriptions are mail merged in.

This is described in greater detail together with “use cases”, blogs and articles on the messagestore.co.uk specialist website.

Merging IR references into the email subject line

The subject line of emails can have mailmerged data in them in the same way as you mail merge data into the body of a document.

The mailmerge templates are created and maintained in Document Template Admin.

Messagestore and Email2IR

Messagestore provides the platform for AXLR8’s Email2IR functionality. Email2IR checks Messagestore for any incoming email and creates a new IR ready for human management decisions:

  1. request type (or you can clik the “Spam” button) and
  2. the applicant (add new or allocate to a previous “frequent flier”).
AXLR8 Email2IR

If there is an exisiting IR reference in the subject line of the incoming email, then that incoming email does not create a new IR. The process checks for whether the email is about an exisiting IRs. It accomplishes this by reading the subject line. If there is and IR code in it, then it will add it to the “job bag” for that IR.

Please call if you need any training on this area or have any concerns about controlling visibility of emails for different groups of users.

Audit Trail

Messagestore takes a copy of all relevant email messages that enter and leave your business. For example, you might be set up to take any email to or from foi@yourorganisation.gov.uk and dataprotection@yourorganisation.gov.uk.

Messagestore then files them against the recipients and senders and the information request unique identifiers. The unique identifiers are coded into the subject lines in the email templates and the numbers and short descriptions are mail merged in.

This is described in greater detail together with “use cases”, blogs and articles on the messagestore.co.uk specialist website.

Merging IR references into the email subject line

The subject line of emails can have mailmerged data in them in the same way as you mail merge data into the body of a document.

The mailmerge templates are created and maintained in Document Template Admin.

Messagestore and Email2IR

Messagestore provides the platform for AXLR8’s Email2IR functionality. Email2IR checks Messagestore for any incoming email and creates a new IR ready for human management decisions:

  1. request type (or you can clik the “Spam” button) and
  2. the applicant (add new or allocate to a previous “frequent flier”).
AXLR8 Email2IR

If there is an exisiting IR reference in the subject line of the incoming email, then that incoming email does not create a new IR. The process checks for whether the email is about an exisiting IRs. It accomplishes this by reading the subject line. If there is and IR code in it, then it will add it to the “job bag” for that IR.

Please call if you need any training on this area or have any concerns about controlling visibility of emails for different groups of users.

System Administration

This is accomplished in Document Template Admin.
To find Document Template Admin, please select Admin menu (cog on LHS menu in the old system or Super User menu in the new UX). Then select Document Template Admin.
There you will see a list of documents already available.

Medium

  • Letter
  • Email
  • Text (SMS) Message
  • Other

File Types

The format of the email will allow it to present and send in diferent ways.

  • .RTF that can be opened by a wide variety of document readers including MS Word
  • .HTML for formatted emails with colours and different highlights, fonts, embedded hyperlinks
  • .TXT for plain text emails
  • other

Context

A mailing template may be built to work in various different contexts.

  • Contact person only (name address, etc.)
    • Reviews and appeals
  • Information Request where the dates (including due date), short descriptions, subject, exemptions, department, owners and applicants and much more information may be merged in specific to that IR.
  • Activity (task within an activity with a specific owner or team to respond in a department
  • Breach

Subject Line

The subject line determines ti a significan extent whether an email will be opened. You can mail merge fields of data into the subject line of your email template.

Managing AXLR8 Mail Merge Templates
Managing AXLR8 Mail Merge Templates

The scope for automation of tasks is enormous with smart mail merged correspondence available in a couple of clicks.

The documents created are also auto-attached to the Information Request. If you have AXLR8 Messagestore then incoming and outgoing emails will be stored against the Information Request, too.

Trigaware

There are also fully automated emails. These are in addition to the mail merged documents. They are launched by the AXLR8 Trigaware system which are preprogrammed on events. Examples include:

  • auto acknowledgement to applicants including details of their request and the due date
  • alert to the team handling responses
  • reminders at 10 and 5 days before the due date for those esponsible
  • alert when a department officer has added a File or Note to an Information Request.

Some clients have a two dozen of these set up containing alerts that change with conditions.

Trigaware auto emails are explained at length elsewhere.

Automation

This is accomplished in Document Template Admin.
To find Document Template Admin, please select Admin menu (cog on LHS menu in the old system or Super User menu in the new UX). Then select Document Template Admin.
There you will see a list of documents already available.

Medium

  • Letter
  • Email
  • Text (SMS) Message
  • Other

File Types

The format of the email will allow it to present and send in diferent ways.

  • .RTF that can be opened by a wide variety of document readers including MS Word
  • .HTML for formatted emails with colours and different highlights, fonts, embedded hyperlinks
  • .TXT for plain text emails
  • other

Context

A mailing template may be built to work in various different contexts.

  • Contact person only (name address, etc.)
    • Reviews and appeals
  • Information Request where the dates (including due date), short descriptions, subject, exemptions, department, owners and applicants and much more information may be merged in specific to that IR.
  • Activity (task within an activity with a specific owner or team to respond in a department
  • Breach

Subject Line

The subject line determines ti a significan extent whether an email will be opened. You can mail merge fields of data into the subject line of your email template.

Managing AXLR8 Mail Merge Templates
Managing AXLR8 Mail Merge Templates

The scope for automation of tasks is enormous with smart mail merged correspondence available in a couple of clicks.

The documents created are also auto-attached to the Information Request. If you have AXLR8 Messagestore then incoming and outgoing emails will be stored against the Information Request, too.

Trigaware

There are also fully automated emails. These are in addition to the mail merged documents. They are launched by the AXLR8 Trigaware system which are preprogrammed on events. Examples include:

  • auto acknowledgement to applicants including details of their request and the due date
  • alert to the team handling responses
  • reminders at 10 and 5 days before the due date for those esponsible
  • alert when a department officer has added a File or Note to an Information Request.

Some clients have a two dozen of these set up containing alerts that change with conditions.

Trigaware auto emails are explained at length elsewhere.

Mailmerge Context

This is accomplished in Document Template Admin.
To find Document Template Admin, please select Admin menu (cog on LHS menu in the old system or Super User menu in the new UX). Then select Document Template Admin.
There you will see a list of documents already available.

Medium

  • Letter
  • Email
  • Text (SMS) Message
  • Other

File Types

The format of the email will allow it to present and send in diferent ways.

  • .RTF that can be opened by a wide variety of document readers including MS Word
  • .HTML for formatted emails with colours and different highlights, fonts, embedded hyperlinks
  • .TXT for plain text emails
  • other

Context

A mailing template may be built to work in various different contexts.

  • Contact person only (name address, etc.)
    • Reviews and appeals
  • Information Request where the dates (including due date), short descriptions, subject, exemptions, department, owners and applicants and much more information may be merged in specific to that IR.
  • Activity (task within an activity with a specific owner or team to respond in a department
  • Breach

Subject Line

The subject line determines ti a significan extent whether an email will be opened. You can mail merge fields of data into the subject line of your email template.

Managing AXLR8 Mail Merge Templates
Managing AXLR8 Mail Merge Templates

The scope for automation of tasks is enormous with smart mail merged correspondence available in a couple of clicks.

The documents created are also auto-attached to the Information Request. If you have AXLR8 Messagestore then incoming and outgoing emails will be stored against the Information Request, too.

Trigaware

There are also fully automated emails. These are in addition to the mail merged documents. They are launched by the AXLR8 Trigaware system which are preprogrammed on events. Examples include:

  • auto acknowledgement to applicants including details of their request and the due date
  • alert to the team handling responses
  • reminders at 10 and 5 days before the due date for those esponsible
  • alert when a department officer has added a File or Note to an Information Request.

Some clients have a two dozen of these set up containing alerts that change with conditions.

Trigaware auto emails are explained at length elsewhere.

Messagestore takes a copy of all relevant email messages that enter and leave your business. For example, you might be set up to take any email to or from foi@yourorganisation.gov.uk and dataprotection@yourorganisation.gov.uk.

Messagestore then files them against the recipients and senders and the information request unique identifiers. The unique identifiers are coded into the subject lines in the email templates and the numbers and short descriptions are mail merged in.

This is described in greater detail together with “use cases”, blogs and articles on the messagestore.co.uk specialist website.

Merging IR references into the email subject line

The subject line of emails can have mailmerged data in them in the same way as you mail merge data into the body of a document.

The mailmerge templates are created and maintained in Document Template Admin.

Messagestore and Email2IR

Messagestore provides the platform for AXLR8’s Email2IR functionality. Email2IR checks Messagestore for any incoming email and creates a new IR ready for human management decisions:

  1. request type (or you can clik the “Spam” button) and
  2. the applicant (add new or allocate to a previous “frequent flier”).
AXLR8 Email2IR

If there is an exisiting IR reference in the subject line of the incoming email, then that incoming email does not create a new IR. The process checks for whether the email is about an exisiting IRs. It accomplishes this by reading the subject line. If there is and IR code in it, then it will add it to the “job bag” for that IR.

Please call if you need any training on this area or have any concerns about controlling visibility of emails for different groups of users.

Data Merge Fields

This is accomplished in Document Template Admin.
To find Document Template Admin, please select Admin menu (cog on LHS menu in the old system or Super User menu in the new UX). Then select Document Template Admin.
There you will see a list of documents already available.

Medium

  • Letter
  • Email
  • Text (SMS) Message
  • Other

File Types

The format of the email will allow it to present and send in diferent ways.

  • .RTF that can be opened by a wide variety of document readers including MS Word
  • .HTML for formatted emails with colours and different highlights, fonts, embedded hyperlinks
  • .TXT for plain text emails
  • other

Context

A mailing template may be built to work in various different contexts.

  • Contact person only (name address, etc.)
    • Reviews and appeals
  • Information Request where the dates (including due date), short descriptions, subject, exemptions, department, owners and applicants and much more information may be merged in specific to that IR.
  • Activity (task within an activity with a specific owner or team to respond in a department
  • Breach

Subject Line

The subject line determines ti a significan extent whether an email will be opened. You can mail merge fields of data into the subject line of your email template.

Managing AXLR8 Mail Merge Templates
Managing AXLR8 Mail Merge Templates

The scope for automation of tasks is enormous with smart mail merged correspondence available in a couple of clicks.

The documents created are also auto-attached to the Information Request. If you have AXLR8 Messagestore then incoming and outgoing emails will be stored against the Information Request, too.

Trigaware

There are also fully automated emails. These are in addition to the mail merged documents. They are launched by the AXLR8 Trigaware system which are preprogrammed on events. Examples include:

  • auto acknowledgement to applicants including details of their request and the due date
  • alert to the team handling responses
  • reminders at 10 and 5 days before the due date for those esponsible
  • alert when a department officer has added a File or Note to an Information Request.

Some clients have a two dozen of these set up containing alerts that change with conditions.

Trigaware auto emails are explained at length elsewhere.

Messagestore takes a copy of all relevant email messages that enter and leave your business. For example, you might be set up to take any email to or from foi@yourorganisation.gov.uk and dataprotection@yourorganisation.gov.uk.

Messagestore then files them against the recipients and senders and the information request unique identifiers. The unique identifiers are coded into the subject lines in the email templates and the numbers and short descriptions are mail merged in.

This is described in greater detail together with “use cases”, blogs and articles on the messagestore.co.uk specialist website.

Merging IR references into the email subject line

The subject line of emails can have mailmerged data in them in the same way as you mail merge data into the body of a document.

The mailmerge templates are created and maintained in Document Template Admin.

Messagestore and Email2IR

Messagestore provides the platform for AXLR8’s Email2IR functionality. Email2IR checks Messagestore for any incoming email and creates a new IR ready for human management decisions:

  1. request type (or you can clik the “Spam” button) and
  2. the applicant (add new or allocate to a previous “frequent flier”).
AXLR8 Email2IR

If there is an exisiting IR reference in the subject line of the incoming email, then that incoming email does not create a new IR. The process checks for whether the email is about an exisiting IRs. It accomplishes this by reading the subject line. If there is and IR code in it, then it will add it to the “job bag” for that IR.

Please call if you need any training on this area or have any concerns about controlling visibility of emails for different groups of users.

Message Store

Messagestore takes a copy of all relevant email messages that enter and leave your business. For example, you might be set up to take any email to or from foi@yourorganisation.gov.uk and dataprotection@yourorganisation.gov.uk.

Messagestore then files them against the recipients and senders and the information request unique identifiers. The unique identifiers are coded into the subject lines in the email templates and the numbers and short descriptions are mail merged in.

This is described in greater detail together with “use cases”, blogs and articles on the messagestore.co.uk specialist website.

Merging IR references into the email subject line

The subject line of emails can have mailmerged data in them in the same way as you mail merge data into the body of a document.

The mailmerge templates are created and maintained in Document Template Admin.

Messagestore and Email2IR

Messagestore provides the platform for AXLR8’s Email2IR functionality. Email2IR checks Messagestore for any incoming email and creates a new IR ready for human management decisions:

  1. request type (or you can clik the “Spam” button) and
  2. the applicant (add new or allocate to a previous “frequent flier”).
AXLR8 Email2IR

If there is an exisiting IR reference in the subject line of the incoming email, then that incoming email does not create a new IR. The process checks for whether the email is about an exisiting IRs. It accomplishes this by reading the subject line. If there is and IR code in it, then it will add it to the “job bag” for that IR.

Please call if you need any training on this area or have any concerns about controlling visibility of emails for different groups of users.

Mail Merge

This is accomplished in Document Template Admin.
To find Document Template Admin, please select Admin menu (cog on LHS menu in the old system or Super User menu in the new UX). Then select Document Template Admin.
There you will see a list of documents already available.

Medium

  • Letter
  • Email
  • Text (SMS) Message
  • Other

File Types

The format of the email will allow it to present and send in diferent ways.

  • .RTF that can be opened by a wide variety of document readers including MS Word
  • .HTML for formatted emails with colours and different highlights, fonts, embedded hyperlinks
  • .TXT for plain text emails
  • other

Context

A mailing template may be built to work in various different contexts.

  • Contact person only (name address, etc.)
    • Reviews and appeals
  • Information Request where the dates (including due date), short descriptions, subject, exemptions, department, owners and applicants and much more information may be merged in specific to that IR.
  • Activity (task within an activity with a specific owner or team to respond in a department
  • Breach

Subject Line

The subject line determines ti a significan extent whether an email will be opened. You can mail merge fields of data into the subject line of your email template.

Managing AXLR8 Mail Merge Templates
Managing AXLR8 Mail Merge Templates

The scope for automation of tasks is enormous with smart mail merged correspondence available in a couple of clicks.

The documents created are also auto-attached to the Information Request. If you have AXLR8 Messagestore then incoming and outgoing emails will be stored against the Information Request, too.

Trigaware

There are also fully automated emails. These are in addition to the mail merged documents. They are launched by the AXLR8 Trigaware system which are preprogrammed on events. Examples include:

  • auto acknowledgement to applicants including details of their request and the due date
  • alert to the team handling responses
  • reminders at 10 and 5 days before the due date for those esponsible
  • alert when a department officer has added a File or Note to an Information Request.

Some clients have a two dozen of these set up containing alerts that change with conditions.

Trigaware auto emails are explained at length elsewhere.

Messagestore takes a copy of all relevant email messages that enter and leave your business. For example, you might be set up to take any email to or from foi@yourorganisation.gov.uk and dataprotection@yourorganisation.gov.uk.

Messagestore then files them against the recipients and senders and the information request unique identifiers. The unique identifiers are coded into the subject lines in the email templates and the numbers and short descriptions are mail merged in.

This is described in greater detail together with “use cases”, blogs and articles on the messagestore.co.uk specialist website.

Merging IR references into the email subject line

The subject line of emails can have mailmerged data in them in the same way as you mail merge data into the body of a document.

The mailmerge templates are created and maintained in Document Template Admin.

Messagestore and Email2IR

Messagestore provides the platform for AXLR8’s Email2IR functionality. Email2IR checks Messagestore for any incoming email and creates a new IR ready for human management decisions:

  1. request type (or you can clik the “Spam” button) and
  2. the applicant (add new or allocate to a previous “frequent flier”).
AXLR8 Email2IR

If there is an exisiting IR reference in the subject line of the incoming email, then that incoming email does not create a new IR. The process checks for whether the email is about an exisiting IRs. It accomplishes this by reading the subject line. If there is and IR code in it, then it will add it to the “job bag” for that IR.

Please call if you need any training on this area or have any concerns about controlling visibility of emails for different groups of users.

Mail Merge Signatory

Messagestore takes a copy of all relevant email messages that enter and leave your business. For example, you might be set up to take any email to or from foi@yourorganisation.gov.uk and dataprotection@yourorganisation.gov.uk.

Messagestore then files them against the recipients and senders and the information request unique identifiers. The unique identifiers are coded into the subject lines in the email templates and the numbers and short descriptions are mail merged in.

This is described in greater detail together with “use cases”, blogs and articles on the messagestore.co.uk specialist website.

Merging IR references into the email subject line

The subject line of emails can have mailmerged data in them in the same way as you mail merge data into the body of a document.

The mailmerge templates are created and maintained in Document Template Admin.

Messagestore and Email2IR

Messagestore provides the platform for AXLR8’s Email2IR functionality. Email2IR checks Messagestore for any incoming email and creates a new IR ready for human management decisions:

  1. request type (or you can clik the “Spam” button) and
  2. the applicant (add new or allocate to a previous “frequent flier”).
AXLR8 Email2IR

If there is an exisiting IR reference in the subject line of the incoming email, then that incoming email does not create a new IR. The process checks for whether the email is about an exisiting IRs. It accomplishes this by reading the subject line. If there is and IR code in it, then it will add it to the “job bag” for that IR.

Please call if you need any training on this area or have any concerns about controlling visibility of emails for different groups of users.

Mail Merge Medium

Messagestore takes a copy of all relevant email messages that enter and leave your business. For example, you might be set up to take any email to or from foi@yourorganisation.gov.uk and dataprotection@yourorganisation.gov.uk.

Messagestore then files them against the recipients and senders and the information request unique identifiers. The unique identifiers are coded into the subject lines in the email templates and the numbers and short descriptions are mail merged in.

This is described in greater detail together with “use cases”, blogs and articles on the messagestore.co.uk specialist website.

Merging IR references into the email subject line

The subject line of emails can have mailmerged data in them in the same way as you mail merge data into the body of a document.

The mailmerge templates are created and maintained in Document Template Admin.

Messagestore and Email2IR

Messagestore provides the platform for AXLR8’s Email2IR functionality. Email2IR checks Messagestore for any incoming email and creates a new IR ready for human management decisions:

  1. request type (or you can clik the “Spam” button) and
  2. the applicant (add new or allocate to a previous “frequent flier”).
AXLR8 Email2IR

If there is an exisiting IR reference in the subject line of the incoming email, then that incoming email does not create a new IR. The process checks for whether the email is about an exisiting IRs. It accomplishes this by reading the subject line. If there is and IR code in it, then it will add it to the “job bag” for that IR.

Please call if you need any training on this area or have any concerns about controlling visibility of emails for different groups of users.