You have a user who is very, very good at handling insurance claims and rubbish at software development and on writing down user requirements.
The user stories are your job as the software developer. Or better yet, your manager’s job who doesn’t care about technical difficulties but about what users need. In that case you should have an opinion about the cost that different options have and tell them - whoever sets user requirements shouldn’t be influenced by their likely wrong opinion of cost.
In other words, you might tell the manager “you have nine points in your user story. Eight of them are easy and can be done in a week each, but the ninth is very difficult and will take 8 weeks alone”. It’s then up to the manager if he wants eight points in eight weeks or nine points in 16 weeks. The manager should not guess what is how hard, because if he gets it wrong, easy tasks won’t be done.