Spaces

The first-reply checklist for library and archive enquiries

This checklist shows what the first reply to a new library, archive or information service message should include, so a member or researcher gets a useful answer straight away. It is made for the people who run these services.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

People write to a library or archive with a small, practical need: a renewal before the fine starts, a reading room visit before they travel, a scan for a deadline. If the first reply is slow or vague, they give up or turn up at the wrong door. The first reply sets the tone for the whole request.

Read each point below and tick the ones you already do. Every gap is something to fix in how you, your desk staff or your AI agent first answers. Print it for the front desk, or read it aloud at a team meeting before a busy week.

Tick each one as you go. 0 of 10 done.

[ ] Greet the person and name your library, archive or service.
[ ] Answer the question asked in the first line.
[ ] Say which branch or reading room the answer applies to.
[ ] Give today's opening hours if they are planning a visit.
[ ] Say what to bring, such as a card or photo identification.
[ ] For a research request, ask for names, places, dates and purpose.
[ ] Be honest about what you do not know yet.
[ ] Point to the right self-service page or form when there is one.
[ ] Say how long a request normally takes.
[ ] End with one clear next step.

What a strong first reply sounds like

Think of the best librarian you have met. They answer, they point, and they ask one useful question back. A first reply in chat should do the same. For example: Hi, thanks for writing to {business}. The reading room is open until four today. Could you tell me which papers and years you would like to see?

That reply answers the question, sets the limit of the day and starts the research request in one short message. Anything longer tends to bury the answer.

Slips that frustrate members

These are the mistakes we would watch for in a service that answers questions all day.

  • Quoting hours for the main branch to someone asking about a smaller one.
  • Telling a researcher that a collection is open before staff have checked.
  • Asking for five details at once, so the person gives up.
  • Replying with a link and no sentence of explanation.

FAQ

How fast should the first reply to a member be?

As fast as you reasonably can during opening hours. A short, helpful reply within minutes beats a perfect one sent next week, especially when a visit or a deadline depends on it.

Should the first reply say whether a record exists?

Only if your written guide clearly says so. Access rules depend on dates and conditions, so otherwise collect the details and tell the person a member of staff will check.

What if the person does not reply to my question?

Leave the chat open. If they were midway through a request, one polite nudge later is fine, because they wrote first. Do not keep chasing them after that.

More free tools for libraries, archives and information services

Read the guide: Answer library, archive and information service enquiries in chat.