Weftd back to homepage

Weftd for local governments

When a resident asks an AI a question, who speaks for your town?

Your information already exists, but it's scattered across the town's website, documents, directories, and staff knowledge. Weftd gathers it into a space your teams can verify, date, and keep up to date.

A town hall building.

Your town

AI Presence

I'm moving in September with a child: what steps do I need to take?

Mairie de Verlon

Local government · Auvergne-Rhône-Alpes

Public service · Updated Sept. 2026

View services & hours
Services & procedures
Opening hours
Contacts & departments
Events & news
01

The shift

The answer is now built before the click.

A resident no longer just searches "town hall + city name." They describe their situation and expect a directly usable answer, forming an idea of the process before ever opening the town's website.

Yesterday

A search, then several pages to check

The resident found the town's website, opened several sections, and pieced the answer together themselves.

"town hall opening hours"
Today

A precise question, then a written answer

The assistant interprets the request, consults the sources it has access to, and composes an answer. It only points the resident to the town's own channels in certain cases.

"I'm moving in September with a child: what steps do I need to take?"
Being found is no longer enough. The town also needs to be identifiable as the official source of the answer.
02

The operational risk

When the answer is wrong, it's often the front desk that has to fix it.

A summer schedule, a deadline, or a local exception can be up to date on the town's website and outdated everywhere else. The assistant doesn't always flag these gaps.

The information an assistant can consult

  • Service pages
  • PDFs and municipal bulletins
  • Third-party directories and portals
  • Events calendar and social media
  • Answers routinely given at the front desk
  • Practical knowledge held by staff
01

An unnecessary trip

The resident acts on incomplete or outdated information.

02

Correction time for staff

The expected time savings turns into time spent verifying and explaining.

03

A misunderstood responsibility

To the resident, the answer is the town hall's, even when it came from a third-party assistant.

Two paths to an answer: an unmanaged third-party copy, and a verified official source.
03

Three audiences

Different needs, the same official information.

Residents, visitors, and partners don't ask the same questions. All of them need information that's understandable, up to date, and validated by the town.

01

Make procedures easier to follow

Opening hours, required documents, fees, conditions, deadlines, and the right department to contact: the knowledge base answers recurring questions and points to the portal as soon as an action is needed.

  • Civil status
  • After-school care
  • Waste collection
  • Urban planning
04

The Weftd method

Organize the information before rolling it out to new services.

Weftd gathers the town's information into a knowledge space called a "Space." Your teams can structure it, verify it, and keep it up to date before it's used across different touchpoints.

  1. 01

    Gather

    Web pages, documents, bulletins, event calendars, directories, open data, and information entered by departments.

  2. 02

    Structure

    Hours, conditions, deadlines, contacts, application periods, sources, and the links between pieces of information.

  3. 03

    Validate

    The relevant teams correct, date, and publish the information. Nothing becomes official without their approval.

  4. 04

    Distribute

    The information can feed a conversational page, a module built into the website, an API, or compatible assistants.

  5. 05

    Improve

    The questions being asked reveal missing answers and content that still needs to be completed.

For every piece of information, the town keeps four reference points

  • The original page or document
  • The period it applies to
  • The responsible department
  • The date it was last validated

What Weftd doesn't replace

Weftd replaces neither the town's website, nor its e-government portal, nor its business software. It complements these tools and points to the right one whenever an action or human verification is needed.

What the source changes

Less copied information. More control.

01

Traceable information

Every piece of information used in an answer can be linked to a source, a date, and a validation.

02

Front-desk staff refocused on complex cases

Answers to frequent questions are prepared in advance, without removing the option to reach a staff member.

03

A shared base for other uses

The work done for residents can also serve phone reception, staff, and partners.

05

Concrete example

One concrete question, several verified pieces of information.

A sample town, shown to demonstrate the approach. No AI assistant is connected to this page.

User's question

“Is parking paid in the town center in August?”

Information used

  • Parking regulations
  • Application period
  • Streets and lots concerned
  • Date of last validation

Example answer

Parking is free from August 1 to 31 on streets in the town center. It remains paid in the station car park. The answer cites the order published by the town and states its update date.

06

Where to start

Start with the questions that come up every week, not the whole town.

The front desk is often the best first scope. Staff already know these questions, their number is limited, and results can be observed quickly. The knowledge space can then expand, department by department.

  1. 01

    List the recurring questions and the answers actually given.

  2. 02

    Gather the pages, documents, rules, and local exceptions needed to answer them.

  3. 03

    Have each piece of information validated and dated by the relevant department, then identify who is responsible for keeping it up to date.

  4. 04

    Deploy a first touchpoint, spot unanswered questions, then fill in the information.

Three possible indicators to track this first scope

  • 01

    Share of frequent questions with a validated answer

  • 02

    Average time to update a piece of information

  • 03

    Number of unanswered questions detected on the tested touchpoint

Cover of the Weftd whitepaper "AI presence for local governments."
07

The whitepaper

The stakes, the evidence, and a method to get started.

The whitepaper explains how search habits are changing, what that means for local public service, and how to build a controlled presence in the answers produced by assistants.

  • What assistants see (and don't see) about your town
  • Why SEO alone isn't enough to control an answer
  • Three audiences and six types of local governments
  • A gradual method that addresses budget, trust, data, and acceptability

Frequently asked questions

What a local government should know before getting started.

Is this a chatbot to install on the town hall's website?

No. Weftd starts by organizing the town's official information. A conversational interface can then use it, but it's only one touchpoint among others.

Does Weftd replace our website or our e-government portal?

No. The website remains the official channel for publishing information, presenting procedures, and letting residents complete them. Weftd structures the information and points back to the town's tools whenever an action is needed.

Can you guarantee a consumer assistant will use our source?

No. No one controls a third-party assistant's final answer. Weftd makes official information accessible to compatible assistants; whether they use it then depends on the protocols, integrations, and permissions available.

Can a small town realistically take this on?

Yes, by starting with a limited number of frequent questions. Pooling resources with the intermunicipal body, a syndicate, or a public digital operator can also be considered.

How do you keep a human in the loop?

The town's teams verify, date, and publish the information. The answer points to a staff member whenever a situation requires a decision, a case review, or a conversation.

What happens to the data submitted through these forms?

The forms collect your business contact details and any information you choose to add, in order to process your request. Weftd's privacy policy specifies the purposes, retention periods, recipients, and how to exercise your rights. The specific terms for a town's data must be reviewed and contracted for each deployment.

What's the right first scope?

The recurring questions received at the front desk are often the best starting point. They're known to staff, limited in number, and let you quickly spot missing information.

Build the first scope

Your town already has the answers. Make them accessible to assistants without losing control of them.

Let's talk about the questions your staff receive most often, the information already available, and the first touchpoint to equip. The goal isn't to launch a large IT project, but to define a useful, realistic scope.

Administrative procedures top the list of areas where French people expect help from an AI assistant: 34% (Ifop study for Converteo, March 2026).

Weftd × Local governments

Share your details to access the document.

Early access

Leave your email and we'll notify you as soon as Weftd opens up.