Very intuitive. Small glitch where I was asked to provide the container number, which I did, and it mentioned that I wrote it twice; that was not the case. Overall a very good idea, and when it is mature it will definitely attract customers who are struggling to get these kinds of updates on time (very often only after the carrier issues the notice to the forwarder).
Thank you for taking the time to test Dean and to tell us exactly what went wrong. You were right: you gave the container number once. Our page saved your message twice in the LinkedIn mobile browser, and Dean wrongly said you had repeated it. That was our mistake, not yours. What we are changing: a message can never be saved twice, and Dean will never blame a customer for a system glitch. When tracking can't reach a carrier, Dean will say so straight away and offer to calculate from the dates you give him, instead of saying he is retrying. And your point about timing is exactly why we built Dean: so you know about demurrage and detention before the carrier's notice reaches the forwarder. Please try him again; we'd value your view. Bert Bloem, founder, AnchorData